-
Notifications
You must be signed in to change notification settings - Fork 35
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
Delete labels feature #183
Conversation
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.
LGTM.
I've just suggested a few styling changes to keep it consistent with the codebase and setting the delete property default to false
Co-authored-by: Rômulo Vitoi <romvitoi@gmail.com>
Thanks for taking a look @RomuloVitoi - suggestions committed, good idea there with defaulting to false! |
Hi @notlee, any chance to review this PR? 🙏🏼 |
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.
This looks like a great addition to me. Thanks all 👍
That's released in 2.3.0 :) |
Resolves #182
This PR introduces an optional
delete
flag for labels. Whentrue
, matching labels will always be deleted. This can be used in conjunction with theallowAddedLabels
flag to mark a subset of labels for deletion while leaving others intact, allowing more fine-grained control over label management.Labels in the local configuration that are missing in the remote will not be created if they are flagged for deletion in the config.
In order to facilitate overriding
allowAddedLabels
, logic forallowAddedLabels
has been moved down intocalculateLabelDiff
- I considered some alternatives but this felt like the cleanest way to do it, though additional feedback and suggestions are very welcome! Tests and readme have been updated accordingly.