merge

/merge

Use this skill for an existing pull request in the Remotion monorepo.

Loop

Start from the top after every pushed fix, conflict resolution, CI rerun, or other state change:

1. Identify the PR:

gh pr view --json number,url,state,isDraft,baseRefName,headRefName,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup

1. If the PR is draft, closed, blocked by requested changes, missing required approval, or otherwise not eligible to merge for a non-CI reason, stop and report the blocker.

1. If GitHub reports merge conflicts, resolve them using the `pr-ready` workflow. Commit and push the resolution when needed, then start this loop from the top.

1. Wait for checks:

gh pr checks --watch --interval 30

1. If all required checks pass and the PR is mergeable, merge it:

gh pr merge --merge --delete-branch

If the repository or PR clearly requires another merge method, use that method instead.

CI Failures

When checks fail, inspect the failed jobs and logs before deciding what to do:

gh pr checks --watch=false
gh run view <run-id> --json databaseId,status,conclusion,url,jobs
gh run view <run-id> --log-failed

If it is a genuine CI failure:

1. Fix the underlying issue locally, using the `pr-ready` workflow when helpful.
2. Run the targeted local checks, plus broader checks when the change has broad impact.
3. Commit and push the fix.
4. Start the loop from the top.

If it is a CI flake:

1. Use the `flake` skill in this monorepo.
2. Rerun the failed flaky job or failed jobs as directed by that skill.
3. Start the loop from the top.