[docs] Document --push flag safety features (branch validation and user confirmation) #11367
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.
Documentation Updates - 2026-01-22
This PR updates the CLI documentation to reflect the safety features added to the
--pushflag in PR #11343.Changes Made
Updated
docs/src/content/docs/setup/cli.mdto document the new safety features for--pushflag across three commands:gh aw init --pushgh aw run --push--refbranch)gh aw upgrade --pushSafety Features Documented
The documentation now clearly explains that
--pushincludes:CI,CONTINUOUS_INTEGRATION,GITHUB_ACTIONSenv vars)Merged PRs Referenced
Notes
All merged PRs from the last 24 hours were reviewed. Most already included documentation updates:
docs/campaign-discovery-budgets.md)gh aw listcommand #11355 - Workflow count output togh aw list(CLI docs already had the command documented)features.action-mode: scriptfrontmatter (already documented in the PR)The only documentation gap was the
--pushflag safety features, which this PR addresses.