Repositories

A repository holds a project's code and its history together with the work that surrounds it: the issues that track what still needs doing, the merge requests that propose changes, and the settings that decide how the repository behaves. These pages describe the repository area of the Vetrix web UI at gitvetrix.com, in the order you tend to meet it — create a repository and get your bearings, read the code and its history, collaborate on issues and merges, watch the activity, then configure the repository itself.

Where to find it: open a repository from the Repositories page, a search result, a profile, or a direct link to gitvetrix.com/<owner>/<repo>. Its sidebar carries Code, Issues, Merges, Analytics, and Settings, and the settings pages share a second sidebar labelled Repository settings. Some entries in that settings sidebar are documented elsewhere in this guide; see Related pages.

Getting started

Create a repository and learn the landing page you return to every time you open it.

Creating a repository — fill in the create form's name, description, visibility, and default branch, and read what each visibility level exposes before you choose one.
Repository home — the landing page, with the root file list, the rendered README beneath it, the branch selector, the HTTPS and SSH clone URLs, the star and watch buttons, and the watchers list.

Code and history

Read the files, the commits behind them, and the difference between any two points in the history.

Branches and tags — list the branches with how far each has moved ahead of or behind the default branch, list the tags with their commits and dates, start a merge from a branch, and delete a branch or tag behind a typed confirmation.
Browsing code — walk the file tree, read a file with syntax highlighting, link to a single line or a range, open the unformatted raw text, and use blame to see which commit last changed each line.
Commits and the commit graph — read a branch's commit log newest-first, open a single commit for its full message and diff, and draw the branch and merge topology as either a diagram or a table.
Compare changes — pick a base ref and a compare ref to read the diff between them and open a merge request from the result, and learn the diff controls (unified or split, ignore whitespace, mark viewed) used wherever a diff appears.
Symbols — search the functions, classes, types, and constants indexed from the repository's code, narrow the results by kind, and jump straight to a definition.

Issues and merge requests

Track the work, and review the changes proposed against the repository.

Issue detail — read and join one issue's discussion, edit its description, assumptions, and acceptance criteria, link related issues and branches, set its type, priority, status, estimates, labels, milestone, assignees, and parent from the details panel, and close or reopen it.
Issues list — narrow a repository's issues by state, type, priority, label, milestone, status, component, and version, search their text, save a filter combination for reuse, and switch between the flat list and a threaded Epic-to-Task tree.
Merge requests — browse the Merges list, open a proposal, follow its conversation, commits, and CI checks, review the diff line by line, submit an approve, request-changes, or comment decision, and finish with a merge commit, a squash, or a rebase.
Milestones — group issues toward a release or deadline and read each milestone's due date, open and closed counts, and progress bar, with create, edit, and delete controls for anyone with write access.

Activity and analytics

Measure how the repository is being used and how the work is moving.

Repository analytics — a dashboard, open to people with write or admin access, of contributor, push, merge, pipeline pass-rate, and delivery-velocity figures over a time range you choose, with focused views for git traffic, the full contributor leaderboard, pipeline timing, and throttled requests.

Repository settings

Configure how the repository behaves. Most of these pages need owner or administrator access; without it, each explains that you cannot manage that setting.

Branch protection — rules that match branches by pattern and require a number of approvals, gate merges on a passing pipeline, or restrict direct pushes, with each control marked as enforced or recorded for display only, above a read-only list of every branch and whether a rule protects it.
Collaborators and teams — who may work in the repository: add individual people by username or grant a whole team at the Read, Triage, Write, Maintain, or Admin level, change a role afterwards, and revoke access behind a typed confirmation.
General repository settings — the repository's own details: its name, description, default branch, issue-numbering project code, visibility, and the topics keywords, plus the danger zone that deletes it permanently.
Labels and issue types — the two schemes that organise a repository's issues: the coloured labels you create, recolour against an AA contrast check, and delete, and the issue types the repository offers and the order they appear in.
Mirrors — pull mirrors that copy a remote repository into this one on a schedule and push mirrors that replicate every push out to a remote, each with encrypted stored credentials, an on-demand sync, and a sync log.
Rate limits — per-repository request-budget overrides for each traffic scope — API reads, writes, and expensive calls, git reads and writes, registry traffic, and interface telemetry — with the 24-hour throttled count per scope and a Remove action that falls back to the group default.

Vetrix user documentation — the index for the whole user guide.
Pipelines — the CI/CD runs that a repository's merges and branch protection rules can be gated on.
Packages — the packages and container images published alongside a repository.
MCP — the MCP settings entry, which connects AI assistants to the repository.
Webhooks — the Webhooks settings entry, which posts repository events to an external URL.