docs(readme): status badges + clearer setup intro#52
Merged
Conversation
Add ci / nightly-e2e / npm badges. Rewrite the intro to orient newcomers: a one-line "Terraform for GitHub admin" framing, and a new "What you need to run it" section that states the two prerequisites up front (auth — token or a GitHub App; and a config file) and that dry-run is the safe default. 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
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.
Addresses two bits of feedback: surface build/e2e status, and make the intro state plainly what setup someone is in for.
Badges
ci,e2e (nightly), andnpm version— all verified to resolve (200).Intro rewrite
Docs-only.
🤖 Generated with Claude Code