Allow to configure assignees/reviewers when frogbot creates a fix Pull Request
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Describe the solution you'd like to see
I would be great to be able to configure some assignees or reviewers in the repo's frogbot-config.yml, that would be set by frogbot when it creates a Merge Request to fix a vulnerability (when running the scan-and-fix mode).
This way, the repos owners could be triggered when a vulnerability is discovered on a dependency of the project.
Describe alternatives you've considered
Additional context
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 by tracing how frogbot loads frogbot-config.yml and how scan-and-fix creates vulnerability-fix pull requests. Determine where configurable assignees and reviewers would be represented, then verify that generated pull requests receive those settings when configured. No specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100