Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolving Pull request comment from frogbot #775

Closed
build630 opened this issue Oct 29, 2024 · 1 comment · Fixed by #809
Closed

Resolving Pull request comment from frogbot #775

build630 opened this issue Oct 29, 2024 · 1 comment · Fixed by #809
Labels
question Further information is requested

Comments

@build630
Copy link

When we scan the pull request through "frogbot.exe spr", it is adding comment to pull request.

Per branch policies, Active PR comment blocks the completion of PR's and user have to resolve it manually. So, I am checking if there is a way to keep comments as active, only if the PR introduces any vulnerabilities. Otherwise, PR comment should be marked as resolved automatically.

  1. Is there a parameter that is capturing if the PR has any issues or not
  2. Is there a way to configure/mark the pull request comment as completed, if there are no issues.
@build630 build630 added the question Further information is requested label Oct 29, 2024
@eyalk007 eyalk007 linked a pull request Dec 29, 2024 that will close this issue
4 tasks
@eyalk007
Copy link

Hello @build630,

Thank you for using Frogbot!

In the next release of Frogbot, we will offer the option to add this flag:
JF_PR_ADD_SUCCESS_COMMENT

You can use it like this: JF_PR_ADD_SUCCESS_COMMENT=false

This will prevent Frogbot from creating the success comment in your pull requests.
If you have any more questions or need further assistance, please feel free to ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants