labeler
labeler copied to clipboard
An action for automatically labelling pull requests
Exposes the added labels as an output (string). If no labels where added, it returns an empty string. Merging this pull request should close #407.
Currently the action generates the `labels` attributes and sends it to the GitHub API. It would be nice to have it also as an output of the action.
With this change, users no longer need to explicitly pass a `repo-token`
### A possible misbehaviour Existing labels get removed even configured with: ```yml sync-labels: false # which is the default ``` In our repository, we see that the labeler removes an...
Bumps [prettier](https://github.com/prettier/prettier) from 2.6.2 to 2.7.1. Release notes Sourced from prettier's releases. 2.7.1 🔗 Changelog 2.7.0 diff 🔗 Release note Changelog Sourced from prettier's changelog. 2.7.1 diff Keep useful empty...
Assign a label based on the branch name! (Closes #186) Depending on your branch name you may want to apply different labels based on the purpose of the branch. eg....
This is a bit related to #12 and #36, except that it's the other way around. I have a repo (https://github.com/gregsdennis/json-everything), and the labeler always fails on PRs submitted by...
Hello, and thanks for your contribution. I've been trying to add the labels `needs code review` and `needs functional test` to a pull request when it is open, regardless of...
I'm trying to gauge whether to take a dependency on this action (which doesn't do _quite_ what I want; I want to define label configuration throughout the repo not just...