New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port update reference data pipeline to GitHub Actions #2249
Port update reference data pipeline to GitHub Actions #2249
Conversation
6ffa8a8
to
3ef1511
Compare
Codecov Report
@@ Coverage Diff @@
## master #2249 +/- ##
=======================================
Coverage 71.82% 71.82%
=======================================
Files 133 133
Lines 12358 12360 +2
=======================================
+ Hits 8876 8878 +2
Misses 3482 3482
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
*beep* *bop* Hi, human. The Click here to see your results. |
9606d99
to
2ad8b10
Compare
ebde19e
to
248e4bb
Compare
Could you write a short summary (or just docs) describing what the refdata pipeline does now? Is it identical to the Azure version in steps? |
Yes, I could write a summary in the PR body. This is just a port of the pipeline that generates new reference data and opens a pull request in the I'm planning to port |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this PR!
* Create new workflow * Patch for arepo tests * Restore deleted parameter * Black format; Add missing skip reason * Fix typo in comment * Add more comments * Create slash command dispatcher * Changes to dispatcher * Black format * Adapt workflow to run on workflow dispatch; create pull request step * Black format * Minor fixes * Add bot comments after result * Remove Azure Pipelines YAML file * Do not push .lfs-assets-id on pull request
📝 Description
Type: 🎢
infrastructure
This GA workflow replaces the Azure
update-refdata
pipeline, and does exactly the same job: using the slash command/update-refdata
the workflow is called, generates new reference data based on the changes made in the pull request, and then opens a new pull request in thetardis-refdata
repository proposing these changes.dispatch.yml
workflow to allow running other workflows via slash commandsupdate-refdata.yml
workflowCloses #2251
📌 Resources
🚦 Testing
How did you test these changes?
Tested on my fork:
It's unlikely that this workflow works out of the box, but it was tested as much as possible.
☑️ Checklist
build_docs
label