Skip to content
Zide Zide Zide

GitLab Overview

You can use the GitLab Overview tab to view your GitLab project metadata, statistics, and quick links, and to change the project visibility.

Open GitLab Overview

To open the tab, click DevOps > GitLab Overview. When more than one remote is on a supported Git host, the DevOps menu lists those remotes under Sources. Point to the remote and click GitLab Overview. The tab title then includes the remote name, for example GitLab Overview (upstream).

The top of the GitLab Overview tab shows the following information.

  • Project name: The namespace and the name of the project.
  • Visibility badge: Private, Internal, or Public.
  • Stars: The number of stars the project has.
  • Forks: The number of forks the project has.
  • Open Issues: The number of open issues in the project, when issues are turned on.

GitLab does not report the number of open merge requests, so the GitLab Overview tab does not show it.

Below this, the GitLab Overview tab has the Languages, Repository Info, Topics, Visibility, and Open in Browser sections. To close or open a section, click its heading. Zide remembers the sections that you close and keeps them closed in the GitLab Overview tab of every project.

Languages

If the project has content, the Languages section lists the languages that files are written in, by percentage.

Repository Info

The Repository Info section lists the following information about the project.

  • Default Branch: The default branch of the project.
  • License: The license of the project.
  • Created: The creation date of the project.
  • Last Push: The date of the last activity on the project.
  • Disk Usage: The amount of storage space used by the repository.

Topics

The Topics section displays topics applied to the project. To add a new topic, click Add in the Topics section. Enter the topic name in the topic-name field and click Add.

Topic names must be lowercase and contain no spaces.

Visibility

The Visibility section tells who can see the project. When the section is closed, its heading shows the current visibility.

  • Private: Only project members can see the project.
  • Internal: Any signed-in user, except external users, can see the project.
  • Public: Anyone can see the project, without signing in.

To change the visibility, complete the following steps.

  1. In the Visibility section, click Make Private, Make Internal, or Make Public.
  2. Read the consequences in the dialog. To make the project public, type its full path, for example group/project.
  3. Click the same button in the dialog.

Zide updates the GitLab Overview tab, the visibility in the window title, and the project’s access. Zide treats internal projects like private projects. If your Zide plan does not include private repositories, making a public project private or internal locks the project. The dialog tells you before you confirm.

Only project owners can change the visibility. Developers and Maintainers see the buttons unavailable, with the reason. An archived project must be unarchived first. GitLab.com does not offer the internal level, so Make Internal shows only on a self-managed GitLab instance.

If GitLab does not accept the change, the Visibility section shows the reason. For example, a project cannot be more visible than its group, and an administrator can restrict some levels. The visibility does not change.

Open in Browser

The Open in Browser section links to the repository’s pages on GitLab: Repository, Issues, and Merge Requests. The GitLab Docs link opens GitLab’s documentation for help with GitLab itself, rather than a page in your repository.

Click a link, or select it and press Enter, to open the page. By default, it opens in the built-in Web Browser tab.

If your GitLab account is not connected, or the repository details cannot load, the tab shows the reason and the Open in Browser section.