Pull Requests

A pull request compares a head branch with a base branch. It collects the change, discussion, review decisions, and checks that determine whether the branch is ready to merge.

Open a pull request

Commit and push the branch before opening the pull request:

git switch -c feature/short-name
# Edit and test the change.
git add path/to/files
git commit -m "feat: describe the change"
git push -u origin HEAD

try pr create \
  --title "Describe the change" \
  --base main \
  --body-file pr-body.md

Add --draft when the change is not ready for a merge decision. Draft pull requests can still collect discussion and checks; mark the pull request ready from its page when reviewers should treat it as complete.

Before creating another pull request for the current branch, check whether one is already open:

try pr current

This command exits nonzero when the current branch has no open pull request.

Find and update work

The pull request list supports filtering and sorting. On an individual pull request you can edit its title or description, assign people, add or remove reviewers, comment, and move between draft and ready states.

Reviewers can be individual users or organization teams:

try pr request-reviewers NUMBER -R OWNER/NAME \
  --reviewer USERNAME \
  --team-reviewer TEAM_SLUG

Team review requests require a team that can access the organization repository. A requested reviewer is not the same as an approving reviewer; protected branches can block while a review request remains outstanding.

Checks and branch updates

Inspect mergeability and current checks before asking for final review:

try pr status NUMBER -R OWNER/NAME

When the base branch moves, update the pull request branch from the platform:

try pr update-branch NUMBER -R OWNER/NAME --style merge

Use --style rebase only when the repository allows rebase branch updates. If the branches conflict, resolve the conflict locally with Git, then push the resolved branch. The dashboard does not provide a general conflict editor.

Continuous integration reports workflow results as checks. Branch protection may require named checks, approvals, signed commits, or an up-to-date branch before merging.

Review the change

The pull request page supports both unified and split diffs, inline feedback, review conversations, and review decisions. Follow the complete code review workflow, or use the terminal diff viewer for a local review surface.

Close, reopen, or merge

An open pull request can be closed without merging and reopened later. Re-check its state and checks immediately before merging:

try pr view NUMBER -R OWNER/NAME
try pr status NUMBER -R OWNER/NAME
try pr merge NUMBER -R OWNER/NAME \
  --method squash \
  --delete-branch

Repository settings determine whether the dashboard offers a merge commit, squash, or rebase. They also control automatic head-branch deletion and whether maintainers can edit the head branch.

For a GitHub-synchronized repository, a merge can remain queued briefly while GitHub creates the merge commit and the result synchronizes back to Trylle. Do not repeat the merge solely because the first response is still pending; check the pull request state and sync health first.