The labeler action creates the corresponding labels in GitHub if not already created when matches are found. Although this might mean less work is needed to create labels, it also means that a PR might create arbitrary labels if the configuration file is modified in that PR. Some organizations may prefer to avoid this and to have a single way to create labels or more control over them. Also, because that somehow breaks the permission criterion that is required to create a new label on a GitHub repository.
Maybe an option could be added to the configuration of the action preventing it from creating a label if it does not exist in GitHub.
Following #13 (comment).
The
labeleraction creates the corresponding labels inGitHubif not already created when matches are found. Although this might mean less work is needed to create labels, it also means that a PR might create arbitrary labels if the configuration file is modified in that PR. Some organizations may prefer to avoid this and to have a single way to create labels or more control over them. Also, because that somehow breaks the permission criterion that is required to create a new label on aGitHubrepository.Maybe an option could be added to the configuration of the action preventing it from creating a label if it does not exist in
GitHub.Following #13 (comment).