-
-
Notifications
You must be signed in to change notification settings - Fork 26k
MNT Adds autolabler for modules #16520
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
MNT Adds autolabler for modules #16520
Conversation
The failure on the lalaber is because this PR can not run against itself. This is most likely due to permissions. An example of this PR working is here: thomasjpfan#18 (This is a PR on my own fork) |
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 think if a PR touches a lot of modules, then these labels probably don't apply. Can we limit the auto labelling to the case where few modules are touched??
I forked the labeler repo and added a In this PR I set the number to 3. |
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.
Hard to check that this will behave fully as expected once merged, but I guess it's only labels in the end.
Thanks Thomas!
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.
Nice, I think @cmarmo had the same idea at some point
triage: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: thomasjpfan/labeler@master |
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.
question, does this have to be on your user?
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.
From a comment above
I forked the labeler repo and added a max-labels feature
It's probably safer than running third party code from master (or a tag which can be force pushed) anyway.
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 just don't know what this thing does really, trying to understand :D
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 had to update this PR with my v2.2.0
tag.
Let see how it works. My worry is about its maintainability. We could maybe move the |
Looks like it does fail in PRs e.g #16348 (comment)
|
Also email notifications for failed jobs seem to be on,
|
Yes, but this time I didn't even have the time to start working on that... and already saw the PR... ;) |
For details, the This is built into the release |
I see. Should someone push a fix to master? |
* MNT Adds labeler * BUG Fix * Double quotes are better * BUG Fix * MNT Adds build ci tag * MNT Use fork for new feature
* MNT Adds labeler * BUG Fix * Double quotes are better * BUG Fix * MNT Adds build ci tag * MNT Use fork for new feature
Automatically adds labels based on the folder that was changed.