ralph-merge

To automatically merge an approved pull request, this Skill validates its mergeability and approval status before integrating it into the main branch and advancing the associated GitHub issue to the 'Done' state.

Yes, you can move a GitHub issue to the Done state after a pull request is merged by providing the issue number or PR URL, which identifies the associated PR and updates the workflow state upon successful merge.

The best way to merge a pull request and clean up the local worktree is to use an automated workflow that merges the approved PR into the main branch and then removes the associated worktree in a single operation.

To merge a pull request for an epic or group worktree issue, you provide the issue number or PR URL, and the automation identifies the correct PR from the issue context to merge and advance the issue state.

Yes, the merge automation checks if a pull request is approved by validating PR readiness, which includes verifying both the mergeability of the branch and the approval status before proceeding with the merge.

You should not use automated merging for pull requests that lack formal approval, have unresolved merge conflicts, or are not yet ready for integration into the main branch, as the validation checks will prevent the merge.