Count Contributing Developers
Last updated
Last updated
© 2024 JFrog Ltd All Rights Reserved
This feature is supported in JFrog CLI version 2.60.0
The git count-contributors
command allows JFrog users to easily determine the number of Git developers contributing to their code. The counts indicate the number of contributing developers to the default branch.
The command counts the contributing developers for all commits performed within a specified time range. The results are based on email addresses, thus giving you a specific number of unique developers.
We provide several options to obtain the developer count:
A single repository: Analyze a single Git repository by providing the repository name.
Across a project/group: Analyze multiple repositories organized under a project/group by providing the owner command option.
Across multiple Git servers: Analyze repositories across various Git servers by providing a YAML file as an input file with the required parameters outlined below.
This information can be helpful when purchasing an Advanced Security subscription, as the number of developers is often a key factor in pricing.
Supported Git providers:
GitHub
GitLab
Bitbucket
The CLI outputs may include an estimation of the contributing developers based on the input provided by the user. They may be based on third-party resources and databases and JFrog does not guarantee that the CLI outputs are accurate and/or complete. The CLI outputs are not legal advice and you are solely responsible for your use of it. CLI outputs are provided "as is" and any representation or warranty of or concerning any third-party technology is strictly between the user and the third-party owner or distributor of the third-party technology.
The git count-contributors
command can be run from the JFrog CLI with the following syntax:
Single Repository
Required Parameters:
--scm-type
--scm-api-url
--token
--repo-name
Group/Project
Required Parameters:
--scm-type
--scm-api-url
--token
--owner
Multiple Git Servers- YAML File
Sample Output:
Command Option
Description
--scm-type
[Mandatory]
The type of SCM to use for the analysis.
Supported Values: github, gitlab, bitbucket
Example: --scm-type=github
--scm-api-url
[Mandatory]
The base URL of the SCM system's API endpoint.
Format: The full URL, including the protocol Example: --scm-api-url=https://api.github.com
--token
[Mandatory]
The authentication token required to access the SCM system's API. In the absence of a flag, tokens should be passed in the JF_GIT_TOKEN environment variable, or the corresponding environment variables 'JFROG_CLI_GITLAB_TOKEN, JFROG_CLI_GITHUB_TOKEN or JFROG_CLI_BITBUCKET_TOKEN' Example: --token:your_access_token
--owner
[Mandatory]
The owner or organization of the repositories to be analyzed. Format: Depending on the Git provider. On GitHub and GitLab, the owner is typically an individual or an organization, On Bitbucket, the owner can also be a project. In the case of a private instance on Bitbucket, the individual or organization name should be prefixed with '~'. When using this option without a specific repository name, all repositories will be analyzed at the group/project level. Example: owner=your-organization
--months
[Optional]
The number of months to analyze for developer activity. Default: 1
Example: --months=6
--detailed-summary
[Optional]
Generates a more detailed summary of the contributors. Default: false
Example: --detailed-summary=true
--repo-name
[Optional]
List of semicolon-separated(;) repositories names to analyze, If not provided all repositories related to the provided owner will be analyzed. Example: --repo-name=repo1;repo2
--input-file
[Optional]
The path to an input file in YAML format that contains multiple git providers. Example: --input-file="/Users/path/to/file/input.yaml"
--verbose
[Optional]
Enables verbose output, providing more detailed information.