Synchronize the public Git branch with main via a clean commit in an isolated worktree.
npx skills add https://github.com/ongspxm/mobot_skills --skill push-public
Please help me install this Agent Skill. Skill: push-public Source: https://github.com/ongspxm/mobot_skills/tree/main/push-public Command: npx skills add https://github.com/ongspxm/mobot_skills --skill push-public
This Skill automates the process of publishing changes from the 'main' branch to the 'public' branch of a Git repository, ensuring a clean and concise commit history on the public branch without exposing the detailed commit history of the main branch.
main to public: Creates a clean representation of the main branch's current state on the public branch.main branch.public branch that reflect actual changes, rather than a full merge history.main, you want to update the public branch with a single, clean commit that represents the latest stable state, without cluttering the public history with intermediate development commits.Execute the push-public skill to update the public branch with the latest changes from main.
High-intent search queries and answers about installing and using this skill.
To publish a Git main branch to a public branch without merge commits, you can synchronize them by creating a single clean commit on the public branch that reflects the main branch's current state. This prevents intermediate development history from cluttering the public branch.
The best way to keep a public Git branch updated with the latest stable state is to snapshot the main branch. This process stages the differences into a new, focused commit on the public branch rather than exposing the full merge history.
To sync branches in Git without interfering with your primary working directory, you can perform the synchronization in an isolated worktree. This maintains the integrity of both the main working directory and the main branch history during the push process.
Yes, this branching method fetches all remote changes and pulls the latest from the main branch first. It then resets the isolated public worktree to match main, stages the differences, and pushes the new commit to the remote public branch.
You should use a clean commit history for a public branch instead of a standard merge when you want to update the public branch with a single commit representing the latest stable state. This is ideal after merging several features into main, avoiding intermediate development commits on the public remote.
alexanderopCreate isolated git worktrees for feature branches with safety checks.
blaxel-aiMerge feature branches into develop and push to the remote repository.
charchessManage Vixens GitOps pull requests, production promotion, and branch protection.
hojinzsPublish verified local commits to a remote Git branch with pre-push validation.