How to only add label, not remove when PR is opened?
See original GitHub issueI have a labeler action set up for when PR is opened, using all your default settings. The labeler YAML is set up as such (relevant parts listed below):
Docs:
- docs/*
coordinates:
- '**/coordinates/**/*'
When astropy/astropy#11023 was opened, the only file changed was docs/coordinates/apply_space_motion.rst. By the labeler logic, it should apply Docs and coordinates.
However, the PR author already manually applied Docs label at creation time. As a result, the labeler ended up removing the Docs label. Is this a bug? How do I tell it to simply no-op when a label that should be applied is already there?

Hope you can help and thanks for such a useful action!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Managing labels - GitHub Docs
In the labels list, to the right of the label you want to delete, click Delete. Further reading. "Filtering and searching issues and...
Read more >GitHub tips — Add and remove issue labels using the keyboard
Press L while viewing an issue or pull request on GitHub to edit its labels.Type to filter down the list of labels. Add...
Read more >Useful label-based GitHub Actions workflows - Jesse Squires
The first checks if the pull request is merging into the main branch, and if so, it will remove the stacked PR label,...
Read more >Organize assets in Premiere Pro Project panel - Adobe Support
Use bins · Organize bins · Adding, deleting, and opening bins · Change bin behaviors · Bin tips · Label assets · Rename...
Read more >Labels - GitLab Docs
Next to the label you want to edit, select Edit ( ). Select Delete. Promote a project label to a group label. Introduced...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Confirmed, you can work around this bug by setting
in your workflow.
There hasn’t been much progress in the conversation, but I also want to solve this problem. By removing the manually attached tags, the benefits gained by labelar are diminished.