Vetrix Docs

General repository settings

Change a repository's core details from its General settings page: its name, description, default branch, project code, and who can see it. This page also holds the Danger zone, where you delete the repository, and it links to the separate Topics page for the keywords that help people find your work. Only the repository's owner or an instance administrator can open these settings; anyone else sees a message explaining they do not have permission to edit them.

Where to find it

  • URL: gitvetrix.com/<owner>/<repo>/settings
  • Navigation: Open the repository, then go to its Settings. The settings pages share a left sidebar labelled Repository settings; General is the first entry. The sidebar also lists Topics, Collaborators & Teams, Branch Protection, Webhooks, Labels, Issue Types, Mirrors, MCP, and Rate limits.

Edit general settings

The General settings form holds the repository's main details. Change any field, then save.

  1. In Repository name, edit the name. Names may use letters, digits, hyphens, underscores, and dots, and can be up to 100 characters long. Renaming the repository changes its web address, so existing links to the old name stop working.
  2. In Description, add or update a short summary of what the repository is for. The description is optional and can be up to 255 characters.
  3. In Default branch, choose the branch that visitors land on and that new merges target by default. Start typing to filter the repository's branches and tags, then select the one you want.
  4. In Project Code, optionally set a short uppercase code (2 to 10 letters or digits, starting with a letter) that prefixes this repository's issue and merge-request numbers. The code must be unique across the instance. Leave it blank to number issues with digits only.
  5. Choose a Visibility level (see Choose a visibility level below).
  6. Select Save changes. A confirmation appears once the update is stored. Save changes stays disabled until you actually change something.

Choose a visibility level

The Visibility options control who can see the repository. Each option describes what it means as you select it:

  • Public — anyone on the internet can view this repository, including signed-out visitors.
  • Internal — any signed-in user on this instance can view this repository. Signed-out visitors cannot see it.
  • Private — only you and collaborators you explicitly add can view this repository.

Change the level and select Save changes to apply it.

Manage topics

Topics are keywords that help people find and explore your repository. They live on their own Topics page, reachable from Topics in the settings sidebar.

  1. Open Topics. The current topics appear as a row of chips.
  2. In Add a topic, type a keyword and select Add. Use lowercase letters, numbers, and hyphens. A repository can have up to 20 topics.
  3. To drop a topic, select the × on its chip.
  4. Select Save topics to store your changes. The button is disabled until you add or remove a topic.

If you have read-only access to the repository, you can see its topics but cannot change them.

Delete a repository

The Danger zone at the bottom of the General page holds the delete action. Deleting a repository removes it and everything in it permanently, and it cannot be recovered.

  1. In the Danger zone, next to Delete this repository, select Delete repository.
  2. A confirmation dialog opens, marked Destructive action.
  3. In Type "" to confirm, type the repository's name exactly. The confirm button stays disabled until the name matches.
  4. Select Delete repository /. You are returned to your repository list once the repository is deleted.

Troubleshooting

  • Repository name is required. If you clear it or use a character that is not allowed, the field shows the rule it expects and the settings are not saved.
  • If the name you choose is already used by another of your repositories, the Repository name field reports that the name is already in use. Pick a different name and select Save changes again.
  • If a save fails for another reason, a message appears. Correct the problem and select Save changes again.
  • Collaborators and teams — add people and teams to the repository and set their permission levels.
  • Creating a repository — set a repository's name, visibility, and default branch when you first create it.
  • Branches and tags — list and manage the branches you can pick as the default.
  • Repository home — the landing page shaped by the default branch and visibility you set here.