frogbot config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
- I want setup frogbot config in my local repo's and for that i have setup the frogbot-config.yml file and frogbot-scan-pull-request.yml file and frogbot-scan-repository.yml files has been created with required details but unable to config the local bitbucket repo. getting below errors.
PS C:\Users\xxxxxx/biui\biui> frogbot scan-pull-request
16:32:07 [Info] Frogbot version: 2.9.2
16:32:07 [Error] JF_GIT_PROVIDER should be one of: 'github', 'gitlab' or 'bitbucketServer'
after providing the all the export details also still we are unable to run the commands
and
- i have created shell script file for all the cred's in local repo <xxxx.sh> this also getting the error for
- sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2395 100 2395 0 0 1171 0 0:00:02 0:00:02 --:--:-- 1175
Downloading the latest version of Frogbot...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate.
need assistance on it and need to run frogbot-config.yml
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 frogbot-config.yml, frogbot-scan-pull-request.yml, and frogbot-scan-repository.yml, then inspect the environment values used by frogbot scan-pull-request, especially JF_GIT_PROVIDER. Reproduce the command and the provided shell script on the local Bitbucket repository, including the Windows curl error; done means the configuration is accepted and the scan runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100