-
Notifications
You must be signed in to change notification settings - Fork 146
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
chore(ci): define github labels as code #731
base: master
Are you sure you want to change the base?
Conversation
615a118
to
51fd319
Compare
188ec04
to
d949aa3
Compare
d949aa3
to
de8b544
Compare
de8b544
to
fc9d106
Compare
cfc3742
to
b95e6cf
Compare
c9572c1
c9572c1
to
7ecd91a
Compare
Signed-off-by: Quentin McGaw <[email protected]>
Signed-off-by: Quentin McGaw <[email protected]>
Signed-off-by: Quentin McGaw <[email protected]>
Signed-off-by: Quentin McGaw <[email protected]>
Signed-off-by: Quentin McGaw <[email protected]>
7ecd91a
to
f72eb01
Compare
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v4 | ||
- uses: crazy-max/ghaction-github-labeler@v5 |
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.
I will play the devils advocate here. I'm not sure if using an external action justifies the advantage (at least in daily usage). Maybe I'm not seeing the exact advantage here, but it seems to me that this can just be a 5 min operation if we ever wanted to fully rename all labels (through https://github.com/ava-labs/coreth/labels). Not sure if it's worth to run a 3rd party action in every push/pull. even though the action can be something secure it still adds to the CI overhead.
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.
The aim is to have source-controlled, reviewable (through PRs) Github labels. The rename part is only useful once, for example to rename default label names.
The action also runs in its own workflow only when labels yml files are changed, so it won't pollute on every commit.
Why this should be merged
Allow to track in source control the Github labels, and to easily migrate Github labels (i.e. renames).
How this works
New Github workflow
.github/workflows/labels.yml
usinggithub/labels.yml
as a source for the labels. All the label data was extracted from this API call to keep it the exact same.Removed useless labels according to Darioush 😉
How this was tested
Dry run of labeler job on this PR
Need to be documented?
No
Need to update RELEASES.md?
No