Branch creation (PR) failing at the end for Repository Scans, for a monorepo.
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
On a monorepo with the following frogbot-config.yml (names redacted with *) :
- params:
git:
repoName: test-scan
branches:
- main
scan:
projects:
- workingDirs:
- apps/***/***
- apps/***/***
- apps/***/***
- apps/***/***
- apps/***/***
- apps/***/***
- pathExclusions:
- "*node_modules*"
- "*target*"
- "*venv*"
- "*test*"
- "*analytics*"
I get the following errors at the end:
failed upon creating/checkout branch 'frogbot-formidable-69bab9618eba86d7d6a53b9c9b97213f' with error: a branch named "refs/heads/frogbot-formidable-69bab9618eba86d7d6a53b9c9b97213f" already exists
the following errors occured while fixing vulnerabilities in '/tmp/jfrog.cli.temp.-1708960538-2693089640/apps/***/***':
failed upon creating/checkout branch 'frogbot-semver-cf2fc5578bd663af2e3eaa946400c132' with error: a branch named "refs/heads/frogbot-semver-cf2fc5578bd663af2e3eaa946400c132" already exists
failed upon creating/checkout branch 'frogbot-next-cd954fdff4c346f20cf8413b37af9231' with error: a branch named "refs/heads/frogbot-next-cd954fdff4c346f20cf8413b37af9231" already exists
failed upon creating/checkout branch 'frogbot-word-wrap-e924a4795a0a50023a401dd0ca8b198a' with error: a branch named "refs/heads/frogbot-word-wrap-e924a4795a0a50023a401dd0ca8b198a" already exists
the following errors occured while fixing vulnerabilities in '/tmp/jfrog.cli.temp.-1708960538-2693089640/apps/***/***':
failed upon creating/checkout branch 'frogbot-tough-cookie-55a2094db87e0b506cfe7698b7536175' with error: a branch named "refs/heads/frogbot-tough-cookie-55a2094db87e0b506cfe7698b7536175" already exists
Error: The process '/opt/hostedtoolcache/frogbot/[RELEASE]/x64/frogbot' failed with exit code 1
Could you please help with understanding the problem here?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the frogbot-config.yml project settings and reproduce the monorepo scan using the listed workingDirs and pathExclusions. Trace the repository-scan path that creates or checks out the reported frogbot-* branches; done means the scan completes without duplicate-branch errors and creates the expected pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100