Publish and review a branch

Send finished work from a Project to GitHub and check it through a pull request before it is merged.

The GitHub section of a Project shows its repository mapping only. It does not push a branch or create a worktree for you.

Commit your changes

1. Commit in the checkout or worktree the conversation worked in.
2. Check the branch name, for example with git status.
3. Make sure the mapping's Push repository is where you want this branch to appear.

Publish the branch

1. Ask Chetty to push the branch, or run git push yourself.
2. Wait for the push to finish and read its output.
3. Open the branch on GitHub and confirm the commits are there.

Note: Pushing is a separate action from merging, and both need your authorization. Chetty does not publish on its own initiative.

Review the pull request

1. Ask Chetty to show the pull request, or run gh pr view.
2. Check the automated results with gh pr checks.
3. Create the pull request with gh pr create, or leave a review with gh pr review.
4. Read the review comments and fix anything that is wrong before you ask for a merge.

Keep merging deliberate

Merging changes the shared repository, so it happens only when someone with authority asks for it. Confirm the target branch and the checks before you merge.

Read Autonomy & Safety for how approvals and read-only work limit what a conversation may do.

Related guides

Read Connect GitHub to a Project to set up the mapping this page uses, and Work in a separate Git worktree to keep feature work apart.