chore: add .cve-fix/examples.md guidance for CVE fixer workflow#2780
chore: add .cve-fix/examples.md guidance for CVE fixer workflow#2780theakshaypant wants to merge 1 commit into
Conversation
|
|
There was a problem hiding this comment.
Code Review
This pull request adds a new documentation file .cve-fix/examples.md that outlines guidelines, naming conventions, templates, and best practices for handling CVE fixes and backports. No review comments were provided, and there is no additional feedback on these changes.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
c611ca5 to
b735fa1
Compare
0c8fba1 to
6e7b6d9
Compare
6e7b6d9 to
ebc8fe5
Compare
Generated by /onboard — teaches the CVE fixer workflow how to create fix PRs matching this repo's conventions (branch naming, files that change together, co-upgrades, GOTOOLCHAIN pinning, etc.). Based on analysis of 16 merged CVE/security PRs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Akshay Pant <akpant@redhat.com>
ebc8fe5 to
7b99ccb
Compare
|
@jkhelil is this a hard requirement for auto-CVE fixes? |
|
Closing as the ambient workflow does not necessarily need this example |
Adds
.cve-fix/examples.mdso the CVE fixer workflow knows how tocreate fix PRs matching this repo's conventions.
Patterns extracted from analysis of 16 merged CVE/security PRs:
security-<description>-<release-branch-hyphenated>for code fixes;deps/<package>for dep bumpsgo-jose/v3andgo-jose/v4must always be bumped togetherpkg/adapter/incoming.go,pkg/provider/github/app/token.go,pkg/resolve/remote.gogo.mod(e.g.GOTOOLCHAIN=go1.24.2)📝 Description,🔗 Linked Issue,🧪 Testing Strategy)Generated by
/onboard— run/guidance.updateafter more CVE fixes merge to improve coverage.🤖 Generated by /onboard