migrate-secrets-without-org-owner

To migrate GitHub Actions secrets without organization owner permissions, use a repository-level runner with gh-secret-kit to copy repository and environment secrets. This requires source repository admin access and destination write access to execute the transfer.

Yes, you can migrate environment secrets and variables across repositories using gh-secret-kit via a repo-level runner. The process copies environment settings and secrets from the source repository to the destination through the GitHub API.

Transferring repository secrets requires source repository admin permissions and destination repository write access. A repository-level runner must be set up and torn down using the -R owner/repo flag to facilitate the migration.

Repo-level runner setup for cross-host secret migration involves starting a runner on the source repository, executing migration steps to copy secrets to destinations, and tearing down the runner when finished. This allows multi-repo workflows without org owner access.

Yes, gh-secret-kit supports migrating both repository and environment secrets. It uses the GitHub API to transfer secrets and environment settings, requiring only repository admin permissions on the source and write access on the destination.

Migrating secrets without org access requires a repo-level runner setup and teardown for each migration task, limiting automation scale. It only works if you have source repository admin rights and destination write access, preventing org-level secret transfers.