Repository navigation
Document the update-to-latest-trunk workflow in the README - #137
Merged
Merged
Conversation
The update path (the "Update to latest trunk" menu action, #94) shipped without user-facing docs. This adds a README section explaining that the option is always available on every site, how it fetches, reinstalls and rebuilds, what the amber/red staleness dots mean, and why staleness is judged locally rather than by asking GitHub for the tip of trunk. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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
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 "Update to latest trunk" menu action (#94) shipped without user-facing docs. This adds a README section covering it:
package-lock.jsonmoved, and rebuilds.Docs only — no code changes.
🤖 Generated with Claude Code