Pull Requests

Pull requests (PRs) are the primary way to propose and review changes in VeloGit. This guide covers the full PR lifecycle.

Opening a Pull Request

1. Push your branch to VeloGit.
2. Navigate to the repository and click the Pull Requests tab.
3. Click New Pull Request.
4. Select your source branch and target branch (defaults to main).
5. Add a title and optional description, then click Create Pull Request.

VeloGit will immediately check for merge conflicts. If conflicts exist, they are flagged on the PR before any review begins.

Reviewers and Assignees

From the PR sidebar you can add:

• Requested Reviewers — team members you’d like to review the changes. They appear on the PR and can submit a formal review.
• Assignees — the person(s) responsible for driving the PR to completion.

Both lists use your organization’s member roster. Type a member’s name or email to search.

Reviewing Changes

Open the Files tab to see a unified diff of all changes. You can leave inline comments by clicking on any diff line — these appear anchored to the specific line and file.

Submitting a review

When you’re ready to submit a formal verdict:

1. Click Approve (or Request Changes from the review menu).
2. Add an optional summary comment.
3. Submit. Your review appears on the PR timeline and contributes to the approval count.

Withdrawing a review

If you change your mind, click Withdraw next to your review on the timeline. This removes your approval or change-request from the PR.

Inline Comments

Inline comments are attached to a specific file and line number. They appear in both the Conversation tab (alongside regular comments) and the Files diff view.

• Edit a comment: Click the pencil icon on any comment you authored. Only your own comments can be edited.
• Delete a comment: Click the trash icon on any comment you authored.

Replies to inline comments are threaded beneath the original.

Conflict Detection

VeloGit checks for merge conflicts when a PR is opened and again on each subsequent push to the source branch. If the source branch has diverged from the target in a way that cannot be auto-merged, the PR displays a Conflicts detected warning.

Resolve conflicts locally:

git fetch origin
git checkout your-branch
git merge origin/main      # or rebase — your choice
# resolve conflicts, then:
git push origin your-branch

Once the conflicts are resolved and you push, the PR re-checks and the warning clears.

Merging

When a PR meets all merge requirements (approvals, passing rituals if required by branch protection), the Merge button becomes active. Click it to merge the source branch into the target.

Merged PRs are closed and their source branch can optionally be deleted from the branch list.