Skip to content

docs: cut the README back to what a PR author needs - #10

Merged
jasonappah merged 1 commit into
mainfrom
trim-readme
Sep 18, 2026
Merged

jasonappah merged 1 commit into
mainfrom
trim-readme

Conversation

@jasonappah

Copy link
Copy Markdown
Member

My auto-format docs had grown to 66 lines on a 25-line README — app setup, approval-state semantics, required-check reasoning — none of which someone editing policy.hujson needs to read. The README is back to 27 lines, and the new material is one sentence:

If the check fails, the bot's comment on your PR has a "Format it for me" checkbox — tick it, or comment /fmt, and it'll run the formatter and commit the fix to your branch.

The parts that were worth keeping moved to where their audience already is, rather than being deleted:

  • App setup + the approval behaviour → a comment next to FMT_APP_ID / FMT_APP_PRIVATE_KEY in lint-fix.yml, which is where someone would be looking if they had to recreate the app.
  • Why workflow_dispatch isn't a safe way to re-trigger a stale check → beside the Test ACL step in tailscale.yml, since that step's event gating is the actual reason.
  • Why the lint lives inside the acls job → dropped, because tailscale.yml already said it in a comment. That one was pure duplication.

Also tidies a comment in lint-fix.yml that an earlier patch of mine left mid-sentence ("runs without that click. When / the app secrets are present…").

No behaviour change — comments and Markdown only.

🤖 Generated with Claude Code

The auto-format docs had grown to 66 lines on a 25-line README -- app setup,
approval-state semantics, required-check reasoning -- none of which someone
editing policy.hujson needs. That is now one sentence: the comment has a
checkbox, tick it or say /fmt.

What was worth keeping moved to where its audience already is. The app setup
and the approval behaviour go next to the secrets they describe in lint-fix.yml.
The warning about workflow_dispatch goes beside the Test ACL step whose event
gating is the reason it isn't safe. The note about the lint living inside the
acls job was already a comment in tailscale.yml, so it's simply dropped.

Also tidies a comment in lint-fix.yml that an earlier patch left mid-sentence.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@jasonappah
jasonappah requested a review from a team as a code owner September 18, 2026 17:20
@github-actions

Copy link
Copy Markdown

✅ Policy lint passed

policy.hujson parses and every group member is on its own line.

Lint output
policy.hujson: valid, formatting OK

241bb62 · run log

@jasonappah
jasonappah merged commit 8291e18 into main Sep 18, 2026
2 checks passed
@jasonappah
jasonappah deleted the trim-readme branch September 18, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant