feat: Add scope label mapping and only-existing options + Add label_map as YAML alternative to custom_labels
#47
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.
Add label_map input that provides YAML syntax for mapping task types to custom label names, as an alternative to the JSON-based custom_labels. The two options are mutually exclusive - using both will fail with an error message.
Add two new features for scope label handling:
exist in the repository (do not create new labels)
allowing scopes like "vis" to be labeled as "visualization"