cross-host-secret-migration

Migrate GitHub Actions secrets, variables, deploy keys, and environments between hosts using gh-secret-kit.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/srz-zumix/gh-secret-kit --skill cross-host-secret-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-host-secret-migration
Source: https://github.com/srz-zumix/gh-secret-kit/tree/main/skills/cross-host-secret-migration
Command: npx skills add https://github.com/srz-zumix/gh-secret-kit --skill cross-host-secret-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-host migration of GitHub Actions secrets, variables, deploy keys, and environments using gh-secret-kit to simplify reconfiguration across GitHub.com and GHES.

Core Features & Use Cases

  • Cross-host migration of repository and organization secrets, variables, deploy keys, and environment settings
  • Authenticate to multiple hosts and run structured migration workflows with plan generation
  • Support for HOST/OWNER/REPO and HOST/ORG destination formats to move resources reliably

Quick Start

Run a migration plan to copy all secrets, variables, and environments from a source host to a destination host.

Frequently Asked Questions about cross-host-secret-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate GitHub Actions secrets between GitHub Enterprise Server instances?

Migrate GitHub Actions secrets between GHES instances by authenticating to both source and destination hosts and using gh-secret-kit commands to copy repository and organization secrets, variables, and deploy keys.

Can I move GitHub environments and variables from github.com to GHES?

Yes, you can move GitHub environments and variables from github.com to GHES using cross-host migration commands that support HOST/OWNER/REPO or HOST/ORG destination formats for reliable resource transfer.

What do I need to copy deploy keys across different GitHub hosts?

To copy deploy keys across GitHub hosts, you need to authenticate to both the source and destination hosts and run gh-secret-kit migration workflows that support cross-host destination formats.

Are organization-level secrets supported in cross-host GitHub migrations?

Yes, organization-level secrets are supported in cross-host GitHub migrations, allowing you to move secrets, variables, and environment settings across repository and organization scopes between github.com and GHES.

What is the best way to transfer GitHub Actions secrets without losing environment configurations?

The best way to transfer GitHub Actions secrets without losing configurations is using gh-secret-kit to generate a structured migration plan that copies secrets, variables, deploy keys, and environment settings across hosts safely.

Why does cross-host secret migration require authenticating to both GitHub hosts?

Cross-host secret migration requires authenticating to both GitHub hosts because the tool must read secrets, variables, and deploy keys from the source host and write them to the destination host using separate API credentials.