why: re-anchor from main - #40
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
why-anchors
branch
2 times, most recently
from
July 17, 2026 03:05
ea0e208 to
34fcb3a
Compare
github-actions
Bot
force-pushed
the
why-anchors
branch
from
August 19, 2026 05:47
34fcb3a to
eddd79a
Compare
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.
Mechanical re-anchoring from
main(fa87a3b49ff4d7bf41df7178b7e02e45bcc28b0a).why anchorrewrites onlywhy.anchorsentries — never narrative —so this diff is frontmatter-only. Anchors are stamped here rather
than on the contributing branch because a squash merge discards
branch commits, and an
as_ofmust name a commit main keeps.