chore: add .cve-fix/examples.md guidance for CVE fixer workflow#2780
Open
theakshaypant wants to merge 1 commit into
Open
chore: add .cve-fix/examples.md guidance for CVE fixer workflow#2780theakshaypant wants to merge 1 commit into
theakshaypant wants to merge 1 commit into
Conversation
|
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
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.
theakshaypant
force-pushed
the
add-cve-fix-guidance
branch
from
c611ca5 to
b735fa1
Compare
zakisk
force-pushed
the
add-cve-fix-guidance
branch
2 times, most recently
from
0c8fba1 to
6e7b6d9
Compare
theakshaypant
force-pushed
the
add-cve-fix-guidance
branch
from
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>
theakshaypant
force-pushed
the
add-cve-fix-guidance
branch
from
ebc8fe5 to
7b99ccb
Compare
Member
Author
|
@jkhelil is this a hard requirement for auto-CVE fixes? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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