- Notifications
You must be signed in to change notification settings - Fork359
feat(autolabeler): purge labels that do not match anymore#1433
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
koozz wants to merge2 commits intorelease-drafter:masterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
By starting the set of labels for a pull request with the currentlabels, adding as usual, and purging if configured to purge andcriteria is not met anymore, the actual set of labels can be PUT to thepull request.Fixes:release-drafter#1432Signed-off-by: Jan van den Berg <koozz@linux.com>
Signed-off-by: Jan van den Berg <koozz@linux.com>
ssbarnea approved these changesSep 2, 2025
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.
Very useful fix!
NielsMooren approved these changesSep 2, 2025
NielsMooren commentedSep 2, 2025
I like this, I need this! |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
By starting the set of labels for a pull request with the current labels, adding as usual, and (now) purging if configured to purge and criteria is not met anymore, the actual set of labels can be PUT to the pull request.
This enables mutually exclusive labels to work well. Adding a
majorlabel to a pull request that already has aminorlabel (which is no longer matching the criteria) seems like an unwanted situation. Allowing labels to be 'purged' is basically the same as the functionality from theactions/labelerthat 'owns' labels (which allows it to remove them if the criteria isn't met anymore).Fixes:#1432