A GitHub Action to declaratively sync GitHub labels across repositories using YAML manifests.
action-label-syncer is a GitHub Action that synchronizes GitHub issue and pull request labels using a declarative YAML manifest. It solves the problem of inconsistent or outdated labels across repositories by automating label management as part of CI/CD workflows.
GitHub repository maintainers, open-source project teams, and organizations managing multiple repositories who need consistent labeling practices.
Developers choose action-label-syncer because it provides a simple, declarative way to manage labels across repositories, integrates seamlessly into GitHub Actions workflows, and eliminates manual label maintenance.
GitHub Action to sync GitHub labels in the declarative way
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Labels are defined in a version-controlled YAML file, allowing for reproducible configurations and easy tracking of changes, as shown in the README's manifest examples.
Supports syncing labels to multiple repositories from a central manifest, making it ideal for organizations with many projects to maintain consistency, with configuration examples provided.
The companion label-exporter tool simplifies creating manifests from existing labels, reducing initial setup effort, as recommended in the README.
By default, prunes unlisted labels to keep repositories clean and aligned with the declared configuration, though this is configurable with the prune option.
The action deletes labels not in the manifest by default, which can lead to unintended data loss if not explicitly disabled with prune: false, as noted in the README.
Syncing labels on other repositories requires a personal access token, adding complexity and security considerations beyond the default GITHUB_TOKEN, which the README warns about.
Lacks support for dynamic label rules or event-driven updates, limiting use cases where labels need to adapt based on repository activity, relying solely on YAML files.