Squash merge a GitHub pull request after validation and worktree cleanup.
npx skills add https://github.com/Rachasumanth/text2llm001 --skill merge-pr-rachasumanth
Please help me install this Agent Skill. Skill: merge-pr Source: https://github.com/Rachasumanth/text2llm001/tree/main/.agents/archive/merge-pr-v1 Command: npx skills add https://github.com/Rachasumanth/text2llm001 --skill merge-pr-rachasumanth
This Skill automates the process of merging prepared GitHub Pull Requests (PRs) using a squash merge strategy, ensuring a clean and traceable commit history.
/prepare-pr skill, you can use this skill to finalize the merge, ensuring all safety checks are met and the worktree is cleaned up.Use the merge-pr skill to merge the pull request number 123.
High-intent search queries and answers about installing and using this skill.
To automatically squash merge a GitHub pull request, you can trigger the merge-pr skill with the PR number. It validates checks, ensures the PR is not a draft, and executes the squash merge in an isolated worktree.
No, you cannot automate squash merging draft pull requests. The squash merge process includes safety guardrails that explicitly block draft PRs, require all checks to pass, and prevent direct pushes to main.
The safest way to merge a prepared GitHub PR via CI/CD is using a dedicated worktree for the operation. This method verifies required checks have passed, confirms the branch is up-to-date with main, and cleans up the worktree after merging.
Yes, the automated squash merge process cleans up the Git worktree. It uses a dedicated, isolated worktree specifically for the merge operation and automatically removes it upon successful completion.
Your GitHub pull request fails the automated squash merge if it is still a draft, required status checks have not passed, or the branch is not up-to-date with the main branch. The process enforces these strict checks before merging.
Yes, you need to prepare your GitHub pull request before squash merging. The workflow expects the PR to be fully prepared and reviewed beforehand, ensuring all safety validations are met before the final merge execution.
NJX-njxSquash merge GitHub pull requests with safety checks and branch cleanup.
HorusGoulMerge pull requests by resolving conflicts, checking CI/CD, and squashing via GitHub API.
dyoshikawaAutomates pull request lifecycle including review, CI checks, bug fixes, and merging in GitHub environments.
kubuszokMerges GitHub pull requests while preserving users' verified commit signatures.