Repository navigation
watch: open one pull request a week with the re-confirmed dates and new snapshots - #3
Merged
Merged
Conversation
…ew snapshots After a clean verify, the watch workflow runs tools/mark_checked.py, rebuilds the site, runs the tests and opens (or updates) one pull request from re-confirm/<branch>. mark_checked gains --summary for that pull request's description, keeps a page's old page_updated when its snapshot fails so the next run tries again, and stops asking the Wayback Machine after 3 failures in a row.
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
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.
The archiving that
tools/mark_checked.pydid by hand now runs every Monday as part of the watch workflow.What the weekly watch does now
verify(unchanged): a changed or removed page opens or updates thewatchissue and fails the run.archive(new): when no page changed or disappeared, it runstools/mark_checked.py. Every page's checked date moves forward. Each page Microsoft has updated gets a new Wayback Machine snapshot, which is recorded only if the cited rows are in it. The job then rebuilds the site, runs the tests and opens one pull request fromre-confirm/main. Later runs rebuild that same pull request frommainuntil it is merged.stale(unchanged): goes red when a page hasn't been re-confirmed for 90 days, which now means those pull requests stopped being merged.tools/mark_checked.py--summary FILEwrites the pull request's description: the pages Microsoft updated, their new snapshots, and the pages left alone.page_updated, so the next run tries again. Before this change the date moved forward anyway and the retry was lost.The weekly commits are authored as intikhab49 and committed by github-actions[bot]. A pull request opened by a workflow doesn't start the
ciworkflow, so the archive job runs the tests itself and links that run in the description.Tested
verify,archiveandstalepassed in about a minute. From GitHub's runner it saved a Wayback Machine snapshot ofctc-overview, checked that the snapshot holds the cited rows, re-confirmed 33 of 33 pages, ran the 54 tests and opened Re-confirm cited pages and refresh archived copies (2026-10-13) #2. The data diff was the 33 checked dates plus that page's date and snapshot.Repo setting changed: "Allow GitHub Actions to create and approve pull requests" is now on. The job can't open its pull request without it.
Merge the weekly pull requests with Rebase and merge. When a person squash-merges a pull request opened by github-actions[bot], GitHub credits the bot as the commit's author even when the commit inside is authored by that person (for example
rh-gitops-midstream/releasePR 1764 andj620656786206/vidoPR 774). Rebase and merge keeps the commit authored as intikhab49. Each weekly pull request says this in its description.