[DOCS] partner guide: pass grant_write_access to verify/ while the write window is open - #16
Merged
Merged
Conversation
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.
Bug
"Apply a later release while write access is granted" passed
-var grant_write_access=truetoplanandapply, but not toverify/.verify/has its owngrant_write_accessvariable (defaultfalse), and it checks that the write bindings match it. So on v1.0.3, partners with a correctly open window got:Their projects were correct.
partner-status.sh v1.0.3showed them READY with write granted.Fix
verify/command in that section now passes-var grant_write_access=true.plan,applyandverify/all keep the flag.The v1.0.3 tag keeps the old text. Partners got the corrected command in the group chat. This fixes it for the next release.