Merge requests

A merge request proposes bringing the commits on one branch into another, and gives your team a place to review them first. In Vetrix this area is labelled Merges: it lists the open and closed proposals in a repository, lets you open a new one, and walks a proposal through discussion, line-by-line review, and the final merge. This page covers the merge list, creating a merge, the detail view and its tabs, reviewing the changes, and merging or closing the proposal.

Where to find it

In a repository, select Merges in the sidebar to open the list. From there, New merge starts a proposal and selecting any row opens its detail view.

Merge list: gitvetrix.com/<owner>/<repo>/merges
New merge: gitvetrix.com/<owner>/<repo>/merges/new
Merge detail: gitvetrix.com/<owner>/<repo>/merges/<number>

Older links that use /pulls in place of /merges still work; they redirect to the matching /merges address.

Browse the merge list

Open a repository and select Merges.
Choose a status tab to filter the list: Open, Closed, Draft, or Merged. Open is selected by default and shows proposals that are ready for review. The tab you pick becomes part of the address, so you can bookmark or share a filtered view.
Read the table. Each row shows the Status badge, the merge # number, the Title with any labels beside it, the source and target Branches, the Author, and when it was last Updated.
Select a title to open that merge.
When a filter has more than 25 proposals, use the pager below the table to move between pages.

Each status has its own badge with a matching icon and label, so Open, Closed, Draft, and Merged stay distinguishable without relying on colour. When a filter is empty, the list shows a short "No merges" notice inviting you to open one.

Open a merge

The New merge button appears when you have permission to contribute to the repository.

From the merge list, select New merge.
Set Source branch (from) — the branch that carries your changes — and Target branch (into) — the branch you want them merged into. Start typing in either selector to filter the branch list. The two must be different; choosing the same branch for both shows "Source and target branches must be different." and keeps the create button disabled.
Enter a Title. It is required and limited to 255 characters.
Write an optional Description. The editor has Write and Preview tabs and a formatting toolbar, so you can check how your text renders before you submit.
Optionally add Reviewers, Assignees, and Labels. Each picker is a search box: type to find a person or label, select it to add a chip, and use the chip's remove control to take it back off.
To open the proposal as a work in progress, tick Create as draft.
Select Create merge. Vetrix opens the new merge's detail view. To abandon the form instead, select Cancel.

Read a merge

The detail view opens on the Conversation tab. Across the top you see the status badge, the merge number and title, the source and target branches, who opened it, and when. Below the header are the tabs:

Conversation — the discussion and activity timeline.
Changes — the diff, with a running total of added and removed lines.
Commits — the commits included in the proposal, with a count.
Checks — the CI result for the latest commit.

To the side of the tab row, Reviewers and Review summary open their own panels (described below). On wider screens, a sidebar on the right collects the merge's Labels, Milestone, Assignees, and the merge controls.

Take part in the conversation

Open a merge and stay on the Conversation tab.
Read the timeline. It records comments and replies, submitted reviews, pushed commits, label changes, and state changes, each with the author and time.
To add your own note, write it in the Leave a comment box at the bottom and select Comment.
If new activity arrives while you are reading, a "new comments — click to load" button appears; select it to fold the new entries into the timeline.

Review the changes

Open a merge and select the Changes tab. The badge on the tab shows the added and removed line totals.
Read each file's diff. A summary line reports how many files changed, and a N / M viewed counter tracks your progress.
Select a file's header to collapse or expand its diff. Tick that header's Viewed checkbox once you have finished with a file; the counter updates as you go.
To comment on a specific line, hover over it and select the add-comment control that appears at the start of the row. Write your note in the Write a review comment… box, then select Add comment, or Cancel to discard it.

Submit a formal review

On the merge, select Review summary next to the tabs.
Optionally add an overall note in the summary box. Any line comments you have started are counted at the top of the panel.
Choose a decision: Approve, Request changes, or Comment only.
Select Submit review. Your decision joins the conversation timeline and updates your status in the reviewers list.

To see where each reviewer stands, select Reviewers next to the tabs. Each reviewer is listed with a status badge: Pending, Approved, Changes requested, or Commented.

Check the commits and CI

Select the Commits tab to see the commits in the proposal, newest first. Each entry shows the short commit ID (a link to the full commit), the first line of its message, the author, and when it was made.
Select the Checks tab to see the CI result for the latest commit — whether checks are running, passed, or failed. When the target branch requires a pipeline to pass, a status badge here reports whether that required pipeline has passed, is still running, or failed.

Merge the proposal

Use the Merge controls in the sidebar while the proposal is open.

If reviewers are assigned, wait until every reviewer has approved. Until then the sidebar shows "Awaiting approval from all reviewers." and the merge button stays disabled. A failing required pipeline also blocks merging and explains why.
Optionally tick Delete source branch after merge. This choice is remembered for next time. When the source branch is protected, the option is disabled and marked (protected).
Select Merge… to open the confirmation panel.
Choose a Merge method:
- Create a merge commit — adds a merge commit that keeps the full history of the source branch.
- Squash and merge — combines every commit on the source branch into one commit on the target branch.
- Rebase and merge — replays each source-branch commit onto the target branch with no merge commit.
Select the confirmation button. Its label matches your choice — Confirm merge commit, Confirm squash and merge, or Confirm rebase and merge.

Vetrix completes the merge and updates the proposal's status to Merged.

Close or reopen a merge

To withdraw an open proposal without merging it, select Close merge in the header. Its status changes to Closed.
To pick a closed proposal back up, open it and select Reopen merge. Its status returns to Open.

Browsing code — browse the file tree and read files before you propose a change.
Creating a repository — create a repository and set its default branch.