A GitHub Action that synchronizes secrets from a single source repository to multiple target repositories using regex patterns.
Secrets Sync Action is a GitHub Action that automates the synchronization of secrets from one repository to many others. It solves the problem of manually managing and updating secrets across multiple repositories by allowing maintainers to define secrets centrally and propagate them automatically using regex patterns for selection.
GitHub organization administrators, DevOps engineers, and development teams managing multiple repositories who need consistent secret management and want to reduce manual configuration overhead.
Developers choose Secrets Sync Action because it eliminates the repetitive task of updating secrets individually across repositories, enhances security by centralizing secret rotation, and provides flexible regex-based targeting for precise control over what gets synchronized.
A Github Action that can sync secrets from one repository to many others.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows secrets to be defined and updated in a single source repository, automatically propagating them to others, which reduces manual overhead and ensures consistency.
Uses regex patterns to selectively sync specific secrets and target repositories, providing fine-grained control over what gets synchronized without needing individual configuration.
Supports syncing to GitHub Actions, Codespaces, or Dependabot, enabling adaptable workflow integration based on project requirements.
Includes dry-run mode and concurrency controls to test configurations and avoid hitting GitHub API rate limits, minimizing risks during deployment.
Lacks support for excluding repositories or secrets, requiring complex regex workarounds to skip specific targets, as admitted in the README.
Requires a personal access token with specific scopes; GITHUB_TOKEN won't work, and fine-grained tokens may fail in older GitHub instances, adding setup complexity.
Confined to syncing within GitHub repositories and its integrated services, making it unsuitable for multi-platform or hybrid environments.