Reuse PR dashboard output on state push retries#41
Closed
trask wants to merge 2 commits into
Closed
Conversation
trask
force-pushed
the
pr-dashboard-retry-snapshot
branch
4 times, most recently
from
675bc30 to
4ced65a
Compare
Member
Author
|
closing, found a better direction |
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.
Avoid recomputing expensive PR dashboard results after a state-branch force-with-lease rejection. The first attempt still performs the normal dashboard refresh, then snapshots the generated dashboard state and markdown so later CAS retries can replay those files on top of the latest state branch without refetching PR data.