Question 1

How do I rename a label using GitHub Labeler?

Accepted Answer

Use the `from_name` field in the YAML configuration, as shown in the README example where `wontfix` is renamed to `wontfix_it`. This automates renaming during synchronization without manual intervention.

Question 2

Can GitHub Labeler handle multiple repositories at once?

Accepted Answer

No, it's designed per repository; you need separate workflow and YAML files for each repo. However, you can reuse configurations by copying or templating, but there's no built-in multi-repo sync.

Question 3

GitHub Labeler vs GitHub's native label features: which is better?

Accepted Answer

GitHub Labeler is better for teams wanting automation and consistency through code, while native features suit manual, ad-hoc management. Labeler adds version control and sync but requires setup and YAML maintenance.

Question 4

How to exclude certain labels from being managed?

Accepted Answer

Use the `exclude` input in the workflow to specify patterns, like `help*` or `*issue` in the README example. This prevents the action from modifying labels matching those patterns, preserving them.

Question 5

What happens if the YAML file has syntax errors?

Accepted Answer

The action will fail and labels won't be updated. It's crucial to use dry-run mode in pull requests, as recommended in the workflow, to catch errors before merging changes to the main branch.

Question 6

Does GitHub Labeler work with GitHub Enterprise?

Accepted Answer

Yes, it should work with GitHub Enterprise if GitHub Actions is enabled. Configure the `github-token` input with appropriate secrets, similar to standard GitHub, but verify compatibility with your Enterprise version.

Manage Labels on GitHub (create/rename/update/delete) as Code

What is Manage Labels on GitHub (create/rename/update/delete) as Code?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions