Add --push and --create-pull-request flags to both add and init commands

[Copilot]

gh aw add had --create-pull-request but not --push. gh aw init had --push but not --create-pull-request. Both commands now support both flags.

Changes

gh aw add --push

• Added --push flag that commits and pushes workflow changes after installation
• Signature change: AddWorkflows() and addWorkflowsNormal() now accept push bool parameter
• Reuses existing commitAndPushChanges(), checkOnDefaultBranch(), and confirmPushOperation() helpers
• Commit message format: "chore: add workflow <name>" or "chore: add N workflows"

gh aw init --create-pull-request

• Added --create-pull-request flag (with hidden --pr alias) that creates PR with initialization changes
• Signature change: InitRepository() now accepts shouldCreatePR bool parameter (renamed to avoid conflict with createPR() function)
• Creates temporary branch init-agentic-workflows-NNNN, commits, pushes, and creates PR
• Requires GitHub CLI (gh) to be installed
• Switches back to original branch after PR creation

Example Usage

# Add workflow and automatically push
gh aw add githubnext/agentics/ci-doctor --push

# Initialize and create PR
gh aw init --create-pull-request

Original prompt

---

This section details on the original issue you should resolve

<issue_title>The gh aw add has --create-pull-request, while gh aw init has --push. Both should support both flags.</issue_title>
<issue_description>gh aw add has --create-pull-request

gh aw init has --push

Both commands should support both flags.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes The gh aw add has --create-pull-request, while gh aw init has --push. Both should support both flags. #11913

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.