The transparency that GitClear offers into your code begins by connecting one or more repos to a supported Git providers (including Github, Bitbucket, Gitlab, and Azure Devops). This page will describe how many repos can be imported, how to import them, and the expectations for after importing.


link🎰 Repo import limits

These repo limits are current of June 2021. If you find them to be outdated, please alert us at support@gitclear.com.


linkUsing GitClear via gitclear.com

These limits apply to users who aren't using the Enterprise version of GitClear. You can view our pricing page to confirm the current limits for the subscription tiers.


Trial subscriptions

Users who have not submitted a credit card can import up to three (3) repos with one year of history per repo

Users who have provided a credit card via gitclear.com can import up to ten (10) repos with one year of history per repo


Pro subscriptions

Up to twenty five (25) repos with one year of history per repo


Elite subscriptions

Up to two hundred fifty (250) repos with five years of history per repo


linkUsing GitClear via On Prem Enterprise version

There are pre-set limits for the number of repos that can be imported in the Enterprise version. We will import up to 15 years of history per repo. Be advised that every commit will add incremental size required for the database. As a ballpark, you can estimate that every 10,000 commits processed will consume around 1gb of database space, though this can be optimized by reducing code cached on behalf of viewing diffs.


link🚀 Importing a repo

There are a couple paths to import repos. By default, when you're connecting your account initially, we will direct you to the "repo import" page as one step in the onboarding process. After initiating your initial repo import, you will see a progress bar that can be clicked to view the status of your importing repos, and to add more repos for import.


For users that have passed the "early onboarding" phase where these links are present, you can always add more repos by visiting the "Browse" tab when logged in and clicking the "Add repos" button:


Accessing the "Add a repo" button get the import process underway

You will then be taken to a list of repos, grouped by organization. It will probably look something like this:




Selecting which repos to import to GitClear

Relative to the import limits describe above, you can either select a collection of repos to import from the list, or you can use the "Quick import" box (shown right below "Select a source") if you know the exact organization/path of the repo that you hope to import.


After you have selected all repos to import, scroll to the very bottom of the page and click the "Import selected repositories" button:

The button to initiate a repo import, located at the bottom of the page


link⏳ After repo import is initiated

We will start processing your repo, with the newest commits processed first. The rate at which a repo is imported can vary greatly depending on the number of commits to be processed, how much code is in each commit, how much load other processes are putting on the system, etc. That said, users of gitclear.com should generally expect to see at least 10,000 commits processed per day when their account is being set up. You will observe a bar near the header to appraise you of the status of your repo import(s).



You should see a strip under the header that can be hovered on for details of your importing repo(s)

While data is being processed, many graphs will look incomplete, as the rate at which processed commit data percolates to the various reports varies, and can take up to a day.


linkWhile you wait...

The best next steps to consider for getting the most from GitClear as you await your repo import?


Set up your issue tracker integration with Jira (or non-Jira). This will unlock a much more insightful version of GitClear, allowing you to group work by the issues that the work addressed.

Invite more contributors to the team. The accounts connected to your GitClear entity, the greater the processing quota afforded to us by the git provider. This often accelerates the rate of the repo import.