Say your company doesn't use GitHub, but you still want to continue your contribution graph on your GitHub account.
This tool will scan local repositories, and create a new repository with a series of empty commits that replicate your contributions seen in the local repositories.
Create a configuration file in JSON:
{
"sourceRepositories": {
"paths": [
"<path-to-repo>",
"<path-to-directory-containing-multiple-repos>/*"
],
"possibleBranchNames": ["origin/master", "origin/main"],
"authorEmails": ["<email>"]
},
"contributionsRepository": {
"path": "<repo-path>",
"remote": "origin [email protected]:<username>/<repository>.git",
"includeRepositoryNameInCommits": true
}
}Notes:
sourceRepositories:pathscontains the paths of the local repositories to scan; a path can be:- directly a path to a Git repository,
- or a path to a directory containing multiple Git repositories, in this case, the path must end with
/*.
possibleBranchNamescontains the branch names that will be looked for in the local repositories; once a branch is found, commits will be looked for in it.authorEmailscontains a list of email addresses; the tool will retrieve commits made by these emails addresses.
contributionsRepository:pathcontains the path to the contribution repository; it needs to not exist the first time the tool is run.remote(optional) contains the name and URL of a remote to add to the repo; this will allow you to easily rungit push, potentially with--force, afterwardsincludeRepositoryNameInCommits(optional), iftrue, the name of the repository will be included in commit messages.
Run owncontributiongraph and provide it with the path to the config file:
owncontributiongraph --config=<json-config-file-path>
Push this repo to GitHub, or anywhere else.
On subsequent runs, only new commits will be added to the contribution repository.