deploy-public

Sync private Git repository code to a public GitHub repository.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/wipcomputer/wip-ai-devops-toolbox --skill deploy-public
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-public
Source: https://github.com/wipcomputer/wip-ai-devops-toolbox/tree/main/tools/deploy-public
Command: npx skills add https://github.com/wipcomputer/wip-ai-devops-toolbox --skill deploy-public

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of safely publishing code from a private development repository to its public counterpart, ensuring that sensitive internal files are excluded and releases are synchronized.

Core Features & Use Cases

  • Secure Code Publishing: Automatically copies all files except the ai/ directory and .git/ from a private repository to a designated public repository.
  • Automated Workflow: Creates a pull request on the public repository, merges it, and syncs GitHub releases, streamlining the deployment process.
  • Use Case: After developing a new feature in your private my-app-private repository and running wip-release to create a GitHub release, you can use this Skill to push the code and release notes to the wipcomputer/my-app public repository.

Quick Start

Use the deploy-public skill to sync your private repository located at /path/to/my-app-private to the public repository wipcomputer/my-app.

Frequently Asked Questions about deploy-public

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

FAQPage Schema
How do I sync a private Git repository to a public GitHub mirror?

To sync a private Git repository to a public GitHub mirror, this Skill copies all files except sensitive directories like 'ai/' and '.git/', then automates pull request creation, merging, and release synchronization between the repositories.

How does automated release synchronization between private and public GitHub repositories work?

Automated release synchronization works by using bash and GitHub CLI to copy approved code from a private repository to a public mirror, creating and merging a pull request, and then syncing the corresponding GitHub releases.

Do I need GitHub CLI and bash to automate publishing code from a private repository?

Yes, you need GitHub CLI (gh), git, and bash installed in your environment to automate the secure code publishing pipeline and execute the required pull request and release synchronization commands.

Can I exclude specific sensitive directories when syncing code to a public GitHub repository?

Yes, you can exclude sensitive directories when syncing code to a public GitHub repository; this process automatically filters out the 'ai/' directory and '.git/' folder to ensure secure code deployment.

What is the best way to automate creating and merging pull requests for public repository mirrors?

The best way to automate creating and merging pull requests for public mirrors is using an automated deployment pipeline that securely copies files from your private repository and programmatically manages the pull request lifecycle via GitHub CLI.

Why does my private to public repository sync process fail without GitHub CLI?

Your private to public repository sync process fails without GitHub CLI because the automation relies on the 'gh' command-line tool to authenticate, create pull requests, merge branches, and sync releases between the repositories.