chore(upstream-docs): update watched-document baseline - #79
Merged
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
A watched upstream document moved, or a fetch failure changed its
count, so
upstream-docs-state.jsonno longer describes what thewatcher sees. Merging this makes the new observation the baseline the
next run compares against.
Read the
upstream-docissues this run opened before merging: thisaccepts the new bytes as normal, and on its own says nothing about
whether the registers a driver decodes by have moved.
The required checks do not start on their own here. A pull request
opened with
GITHUB_TOKENstarts no workflow run, so this one arriveswith an empty status rollup. Close and reopen it to run them. The
validaterun dispatched against the branch head is a verdict you canread in the meantime -- GitHub does not count it toward the rollup.
Opened by the
watch-upstream-docsworkflow.