Flag doc changes during staging release #7168
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
|
Size Report 1Affected ProductsNo changes between base commit (3fe7597) and merge commit (b831ba9).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (3fe7597) and merge commit (b831ba9).Test Logs |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Runs a diff against
origin/masteron thedocs-devsitedir during the staging workflow. If a diff is found, it will send adocs_needed=trueparam to the release tracker. I'll make separate changes to the release tracker to then put "docs needed" in the reference CL field and highlight it red.Need to test this, so will wait until after this week's release is done, to not interfere with it.