fix(ci): retry refresh PR creation and validate TechAPI PR deltas - #80
Merged
Merged
Conversation
Member
Author
|
Refs GetTechAPI/TechMachine#1 (weekly-refresh 2026-09-21 failure, techapi-pr-validation-comment repeated failures 2026-09-23). |
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.
Failures addressed
weekly-refreshrun 35593227380 completed validation, integrity checking, and dump generation, thenpeter-evans/create-pull-requestpushedrefresh/2026-09-21but GitHub returnedServer Errorwhile opening the TechAPI PR. The confirmation step now retries the PR API operation up to three times without repeating the scrape.techapi-pr-validation-commentrun 35828297945 and other September 23 runs failed the strict integrity gate on 18 duplicate CPU names already present in the TechAPI PR's base history. The workflow compared changes againstmaineven though TechAPI PRs targetdevelop, causing unrelated changes to appear in the review. It now pins the merge base, reports actual PR changes, and blocks only newly introduced hard integrity anomalies.Verification
integrity_check.pyand passed a fixture covering inherited versus newly introduced duplicate names.git diff --checkpassed.Please use rebase merge after review.