Last modified: May 28, 2024

---

Looking for this interface?

Note:

Your hosting provider can enable or disable this interface in WHM's Feature Manager interface (WHM >> Home >> Packages >> Feature Manager).

Overview

Gitweb allows you to browse your repositories, view file contents, and review log, commit, and other information from within a simple interface. To access the Gitweb interface for a repository, click History for that repository in cPanel’s Git™ Version Control interface (cPanel » Home » Files » Git™ Version Control).

The Gitweb interface

The Gitweb interface displays the project’s summary report.

• The breadcrumbs at the top of the interface display the current repository path and the current report’s name. Click a directory name to view Git repository information for that directory.
  • cPanel’s Git™ Version Control (cPanel » Home » Files » Git™ Version Control) feature enforces several restrictions on repository paths.
  • Repositories on your cPanel account that cPanel does not manage may appear in some lists within the Gitweb interface.
  • You may experience errors if you attempt to view information for repositories in restricted directories.
• Throughout the interface, icons indicate the branches for which a commit is the HEAD commit:
  • Green icons indicate local branches, grey icons indicate remote branches, and yellow icons indicate Git tags. For example, a green master icon () indicates the HEAD commit for the local master branch.
  • Click the branch names in green or yellow icons to view information in the context of that branch rather than the current branch.
• Click the Atom or RSS icons in the bottom-right corner of some reports to access feeds for the repository’s activity.
• Click the TXT or OPML icons in the bottom-right corner of some reports to access plaintext and XML versions of the data, respectively.

Gitweb reports

The Gitweb interface displays repository information as a collection of reports. Gitweb displays links to other reports at the top of the interface and inline with report contents.

blob

Click blob to view the binary large object (blob) for a specific file. Git uses blobs to store the contents of a file at the time of a specific commit. This report displays the following information:

• The name of the commit that contains the file or the SHA-1 identifier for that version of the file, if you accessed this report via the commitdiff report.
• The path to the file within the repository.
  • Click a directory name to view the tree report for that directory
  • Click the filename or raw to view a plaintext version of the file.
• The contents of the file, by line number. Click a line number to navigate directly to that line.

Linked reports

• commit
• commitdiff
• history
• log
• shortlog
• summary
• tree

commit

Click commit to view all of the information for a specific commit. Each commit includes the following information:

• The first line of the commit message, as a header. Click this line to view a commitdiff report that compares this commit and its parent commit.
• author — The commit author’s name, their email address, and the date and time of the commit.
  • Click the author’s name to view the results of a search for that author.
  • Click the author’s email address to view the results of a search for that email address.
• committer — The commiter’s name, their email address, and the date and time of the commit.
  • Click the commiter’s name to view the results of a search for that committer.
  • Click the commiter’s email address to view the results of a search for that email address.
• commit — The commit’s SHA-1 identifier.
• tree — The SHA-1 identifier for the working tree. Click this identifier to view the tree report for the commit.
• parent — The SHA-1 identifier for the parent commit. Click this identifier to view the commit report for the parent commit.
• The full commit message.
• A list of new, updated, moved, or deleted files. Click a filename to view the blob report for that file.
  • New files display the filename and a [new file with mode: 0700] message, where 0700 represents the file’s octal permissions.
  • Updated files display the filename.
  • Moved files display the filename and a [moved from path/name with n% similarity] message, where path/name represents the file’s previous location and n% represents the percentage of the file that resembles its parent version.
  • Deleted files display the filename and a [deleted file] message.

Linked reports

• blob
• commitdiff
• log
• shortlog
• summary
• tree

commitdiff

Click commitdiff (or, in some reports, diff or diff to current) to view a comparison of two commits’ data in the unified diff format (a diff). When you access this report via a commitdiff or diff link, the diff compares the commit with its parent commit. When you access this report via a diff to current link, the diff compares the commit with the HEAD commit.

This report includes the following information:

• The first line of the commit message, as a header.
• author — The commit author’s name, their email address, and the date and time of the commit.
  • Click the author name to view the results of a search for that commit’s author.
  • Click the author email address to view the results of a search for that email address.
• committer — The commiter’s name, their email address, and the date and time of the commit.
  • Click the commiter name to view the results of a search for that committer.
  • Click the commiter email address to view the results of a search for that email address.
• A list of new, updated, moved, or deleted files. Click a filename to view the blob report for that file.
  • New files display the filename and a [new file with mode: 0700] message, where 0700 represents the file’s octal permissions.
  • Updated files display the filename.
  • Moved files display the filename and a [moved from path/name with n% similarity] message, where path/name represents the file’s previous location and n% represents the percentage of lines that the commit changed within the file. Click the file’s previous location to view the blob report for the previous version of the file.
  • Deleted files display the filename and a [deleted file] message.
• The specific git diff command for each file, as a header, and the diff for that file (the output of that command). Click a filename or the short SHA-1 identifier for the file to view the blob report for that file.

In this report, you can also perform the following actions:

• Click inline to view each file’s diff as a list of line-by-line changes.
• Click parent: SHA-1, where SHA-1 represents a SHA-1 identifier, to view the commit report for the parent commit.
• Click patch to view the commit diff in a plaintext email format. You can use this output when you run the git am command.
• Click raw to view a plaintext version of the commit diff.
• Click side by side to view each file’s diff in two columns.

Linked reports

• blob
• commit
• history
• log
• shortlog
• summary
• tree

heads

Click heads to view information about each local branch’s HEAD commit. This report includes the following information:

• The repository path. Click this path to view the summary report for the repository.
• A list of branches that includes the following information:
  • The time since the most recent (HEAD) commit or the commit date.
  • The branch name. Click the branch name to view the shortlog report for that branch.

Linked reports

• commit
• commitdiff
• log
• shortlog
• summary
• tags
• tree

history

Click history to view the change history for a specific file. This report includes the following information:

• The first line of the commit message for the commit through which you accessed the report, as a header. Click the first line of the commit message to view the commit report for that commit.
• The file’s path. Click a directory name to view the tree report for that directory, or click the filename to view the blob report for that file.
• A list of commits that included changes to that file. This list displays the following information:
  • The amount of time since that commit or the commit date.
  • The commit author’s name. Click the author’s name to view the results of a search for that commit author.
  • The first line of the commit message. Click the first line of the commit message to view the commit report for that commit.

Linked reports

• blob
• commit
• commitdiff (diff to current)
• log
• shortlog
• summary
• tree

log

Click log to view each commit’s log information. This report includes the following information:

• The repository path. Click this path to view the summary report for the repository.
• The following information for each of the repository’s commits:
  • The time since the commit (or the commit date) and the first line of the commit message, as headers for each commit. Click the first line of the commit message to view the commit report for that commit.
  • The commit author and the date and time of the commit. Click the author’s name to view the results of a search for that commit author.
  • The full commit message.

Linked reports

• commit
• commitdiff
• shortlog
• summary
• tree

shortlog

Click shortlog to view an abbreviated list of each commit’s log information. This report includes the following information:

• The repository path. Click this path to view the summary report for the repository.

• The following information for each of the repository’s commits:

  • The time since the most recent commit or the commit date.
  • The commit author. Click the author’s name to view the results of a search for that commit author.
  • The first line of the commit message. Click the first line of the commit message to view the commit report for that commit.

Linked reports

• commit
• commitdiff
• log
• summary
• tree

summary

Click summary to view a summary of repository information. This report includes the following information:

• description — The repository’s name and description, if they exist.
• owner — The repository’s owner.
• last change — The date and time of the most recent commit.
• shortlog — Click shortlog to view the shortlog report for the repository. It will contain a list of the following abbreviated log information for each of the repository’s commits:
  • The time since the most recent commit or the commit date.
  • The commit author. Click the author’s name to view the results of a search for that commit author.
  • The first line of the commit message. Click the first line of the commit message to view the commit report for that commit.
• tags — Click tags to view the tags report for the repository. It will contain a list of the following Git tag information:
  • The time since the commit or the commit date.
  • The tag name. Click the tag name to view the commit report for that commit.
  • The tag message. Click the message to view the tag report for that commit.
  • The tag object. Click the tag object to view the tag report for that commit.
• heads — Click heads to view the heads report for the repository. It will contain a list of the following local tracking branch information:
  • The time since the most recent commit or the commit date.
  • The branch name. Click the branch name to view the shortlog report for that branch.

Linked reports

• commit
• commitdiff
• heads
• log
• shortlog
• tags
• tree

tags

Click tags (or, in some reports, tag) to view information about the repository’s tags. If you accessed it for an individual tag, this report lists the following information:

• The tag name, as a header. Click the tag name to view the commit report for that commit.
• object — The SHA-1 identifier for the commit object.
• author — The commit author’s name, their email address, and the date and time of the commit.
  • Click the author’s name to view the results of a search for that commit author.
  • Click the author’s email address to view the results of a search for that email address.
• The tag message.

If you accessed the report via a list of tags, it lists the following information:

• The repository path. Click this path to view the summary report for the repository.
• The following information for each tag:
  • The time since the commit or the commit date.
  • The tag name. Click the tag name to view the commit report for that commit.
  • The tag message. Click the message to view the tag report for that commit.
  • The tag object. Click the tag object to view the tag report for that commit.
  • The first line of the commit message.

Linked reports

• commit
• commitdiff
• heads
• log
• shortlog
• summary
• tree

tree

Click tree to view the working tree for a specific commit. This report lists the following information:

• The first line of the commit message, as a header. Click the first line of the commit message to view the commit report for that commit.
• The following information for each file and directory within the working tree:
  • The symbolic character representation of the file or directory’s permissions.
  • The file size, in bytes, or a hyphen (-) for directories.
  • The file or directory name. Click a directory name to view the tree report for that directory, or click the filename to view the blob report for that file.
    Note:

    • Click snapshot to download the data for this version of the working tree.
    • Click raw to view the plaintext version of a file.

Linked reports

• blob
• commit
• commitdiff
• history
• log
• shortlog
• summary

Search Gitweb data

In addition to Gitweb’s reports, you can search Gitweb for repository information.

To search Gitweb, perform the following steps:

1. From the menu to the left of the search text box in the top-left corner of the interface, select the desired search type:
   • commit — Search for commit authors and messages.
   • grep — Search within the files in the current working tree.
   • author — Search for the commit date, author name, or author email address.
   • committer — Search for a commit date, committer’s name, or committer’s email address.
   • pickaxe — Search for all of the commits that included changes to the specified search terms.
2. Enter the search terms in the search text box.
3. To use Perl-Compatible Regular Expressions (PCREs) in your search text, select the re checkbox.
   Note:

   Gitweb’s PCRE searches are case-insensitive.

4. Press Enter. The search results will appear.