GitHub pull requests
Connect your account, inspect changed files, and collect review comments before submitting them.
Connect GitHub.com
Open Pull requests in the repository header. Opening the panel reads your local remotes and saved drafts. To connect, use Copy sign-in command and run the command in a terminal with GitHub CLI installed.
gh auth login --hostname github.com --web --skip-ssh-key
Complete the browser sign-in, then choose Connect GitHub CLI account in GitTurtle. The authorization is stored in macOS Keychain or the Linux desktop keyring. On Omarchy 4.5, a live check covered connecting the account, opening a pull request, disconnecting and reconnecting through the desktop keyring.
Inspect a pull request
Check the GitHub owner and repository, then choose Refresh PRs. Select a pull request to load its overview, head and base, checks, files and conversations. Files shows the changed-file list. Select a file to inspect GitHub’s patch. A missing or truncated patch can limit which lines accept a comment.
Collect and send a review
- Click a changed line. For a supported range on the same side, Shift-click or use Shift with the arrow keys. Choose Comment on selection or press Enter.
- Write your feedback and choose Add to review. Repeat on other files. The collected comments stay local and retain their original positions.
- In Review, check the comments and choose Comment, Approve or Request changes. A change request needs a summary. Review the destination account, repository, pull request and revision identities before Send to GitHub.
If the head moves, inspect the new revision and reconsider the saved positions. GitTurtle retains the original draft. If a send times out with an uncertain result, check the pull request for your review before submitting again.
Create a pull request
Push the head branch first. In the new pull request form, select the published head and destination base, enter a title and description, and choose Draft or Ready. Review outbound action… resolves both branches. Read the confirmation and choose Send to GitHub. A successful create shows the pull request number. If GitHub reports an existing pull request for the head, open the matching one or refresh the list.
Creation supports a fork head written as owner:branch when the fork and destination share the repository name. GitHub decides whether the connected account can submit a given action.