jfrog / jfrog/jfrog-cli-security

jf git count-contributors with --repo-name parameter not working for lists

Open
#577 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

Describe the bug

Hello,
When using the jf git count-contributors command, we are unable to get results from multiple repos using the --repo-name parameter. Given the error message below, we also tried quoting the list, but it still only shows the results for only the first repo in the list.

Current behavior

~ % jf git cc --scm-type=github --scm-api-url=https://api.github.com/ --token=<my-github-token> --owner=<my-org> --repo-name=<xxx-repo-1>;<xxx-repo-2> --detailed-summary 17:44:31 [Info] Log path: /Users/john.doe/.jfrog/logs/jfrog-cli.2025-08-09.17-44-31.15788.log zsh: command not found: <xxx-repo-2>

~ % jf git cc --scm-type=github --scm-api-url=https://api.github.com/ --token=<my-github-token> --owner=<my-org> --repo-name="<xxx-repo-1>;<xxx-repo-2>" --detailed-summary 17:44:31 [Info] Log path: /Users/john.doe/.jfrog/logs/jfrog-cli.2025-08-09.18-14-30.14944.log

The result only covers the first repo in the list which is <xxx-repo-1> in this example.

Reproduction steps
  1. Download latest JFrog CLI (2.78.2 in this case).
  2. Run the jf git count-contributors command with the --repo-name parameter.
  3. Add more than one repo name to the semicolon-separated list of repositories.
  4. Validate results cover all repositories.
Expected behavior

The results of the command should cover every repositories in the the semicolon-separated list of repositories.

JFrog CLI version

2.78.2

Operating system type and version

MacOS

JFrog Artifactory version

Ent+ 7.111.12

JFrog Xray version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the jf git count-contributors command and its --repo-name argument handling. Reproduce the issue using the semicolon-separated repository names from the report, with and without quoting, on the GitHub SCM configuration. Done means the results include every repository in the list rather than only the first.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.