docs: align README with current codebase and trim over-explanation - #38
Merged
Conversation
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.
Aligns the README with the current code after the recent config-binding, grouped-help, and subject-token-source restructuring. Corrects four factual drifts: the env-var exception list now names all eight flags that lack an
OIDC_TOKEN_*var, the previously undocumented--extraflag is added to the synopsis and flag table, and the Build & Release section now describes the real pipeline (release-please draft plus GoReleaserhomebrew_casks, not svu/brews). Also trims over-explanation in the token-store and token-exchange sections without dropping any load-bearing detail.