Add default branch check and user confirmation to --push flag#11343
Merged
Add default branch check and user confirmation to --push flag#11343
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
pelikhan
approved these changes
Jan 22, 2026
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
|
@copilot if there is NO remote cancel. |
Copilot
AI
changed the title
[WIP] Add validation for push feature in init/upgrade
Add default branch check and user confirmation to --push flag
Jan 22, 2026
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Done. The Fixed in commit 921d75f. Example: $ gh aw init --push
ℹ Checking current branch...
✗ cannot push: --push requires a remote repository to be configured |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 22, 2026
Updates CLI documentation to reflect the safety features added to the --push flag in PR #11343: - Remote repository requirement - Default branch validation - User confirmation prompt (auto-confirmed in CI) Updated documentation for: - gh aw init --push - gh aw run --push - gh aw upgrade --push Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
pelikhan
pushed a commit
that referenced
this pull request
Jan 22, 2026
Updates CLI documentation to reflect the safety features added to the --push flag in PR #11343: - Remote repository requirement - Default branch validation - User confirmation prompt (auto-confirmed in CI) Updated documentation for: - gh aw init --push - gh aw run --push - gh aw upgrade --push Co-authored-by: Claude Sonnet 4.5 <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
--pushflag ininitandupgradecommands now validates the current branch and requires user confirmation before committing/pushing changes.Changes
Remote repository requirement: The
--pushflag now requires a remote repository to be configured. Operations fail immediately with a clear error if no remote exists.Default branch validation: Queries GitHub API to verify current branch matches repository default before pushing.
User confirmation: Prompts for explicit confirmation before mutating git operations. Auto-confirms in CI environments (detected via
CI,CONTINUOUS_INTEGRATION,GITHUB_ACTIONSenv vars).New helper functions (
pkg/cli/git.go):getDefaultBranch()- Fetches default branch viagh apicheckOnDefaultBranch(verbose bool)- Validates branch match and remote existenceconfirmPushOperation(verbose bool)- Interactive confirmation promptBehavior
Before push, the flow now validates:
In CI environments, confirmation is automatic with no prompt shown.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.