Your profile contributions graph is a record of contributions you've made to repositories on your GitHub Enterprise Server instance. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear.
Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork.
Commits will appear on your contributions graph if they meet all of the following conditions:
- The email address used for the commits is associated with your account on your GitHub Enterprise Server instance.
- The commits were made in a standalone repository, not a fork.
- The commits were made:
- In the repository's default branch
- In the
gh-pagesbranch (for repositories with project sites)
For more information on project sites, see "About GitHub Pages."
In addition, at least one of the following must be true:
- You are a collaborator on the repository or are a member of the organization that owns the repository.
- You have forked the repository.
- You have opened a pull request or issue in the repository.
- You have starred the repository.
- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.
- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on your GitHub Enterprise Server instance, receive contribution credit.
After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph.
Commits must be made with an email address that is connected to your account on your GitHub Enterprise Server instance in order to appear on your contributions graph.
You can check the email address used for a commit by adding
.patch to the end of a commit URL, e.g. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch:
From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 From: The Octocat <email@example.com> Date: Sun, 27 Apr 2014 15:36:39 +0530 Subject: [PATCH] updated index for better welcome message
The email address in the
From: field is the address that was set in the local git config settings. In this example, the email address used for the commit is
If the email address used for the commit is not connected to your account on your GitHub Enterprise Server instance, you must add the email address to your account on your GitHub Enterprise Server instance. Your contributions graph will be rebuilt automatically when you add the new address.
Warning: Generic email addresses, such as
firstname.lastname@example.org, cannot be added to GitHub accounts. If you use such an email for your commits, the commits will not be linked to your GitHub profile and will not show up in your contribution graph.
Commits are only counted if they are made in the default branch or the
gh-pages branch (for repositories with project sites). For more information, see "About GitHub Pages."
If your commits are in a non-default or non-
gh-pages branch and you'd like them to count toward your contributions, you will need to do one of the following:
- Open a pull request to have your changes merged into the default branch or the
- Change the default branch of the repository.
Warning: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made.
Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following:
- Open a pull request to have your changes merged into the parent repository.
- To detach the fork and turn it into a standalone repository on your GitHub Enterprise Server instance, contact your site administrator. If the fork has forks of its own, let your site administrator know if the forks should move with your repository into a new network or remain in the current network. For more information, see "About forks."