docs(controller): add patch identity preservation guide#234
Merged
Conversation
4 tasks
4b9fc67 to
583b82c
Compare
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
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.
Summary
docs/controller/addon-controller-patch-identity-preservation-guide.md.docs/controller/README.md.Why
When an addon team has already built and verified a patch image from a controller PR head SHA, that SHA is an evidence anchor. If reviewer feedback is test-only, doc-only, or otherwise does not change production behavior, a follow-up commit keeps that anchor valid. If production behavior must change, the addon verification owner must be told to re-check patch identity against the new SHA.
Test plan
git diff --check origin/main...HEAD