fluid-pr

CRITICAL Add the following steps to your task/todo list using the available Copilot task-management tooling:

1. Confirm you are NOT on main or any release branch. If you are, stop and tell the user: you cannot create a PR from a protected branch — they need to create or switch to a feature branch first.
2. Verify that the origin remote does not point to microsoft/FluidFramework. If it does, stop and tell the user: pushing a branch directly to the main repo is not allowed — they should push to their fork instead. Pipeline changes on branches prefixed with test/ are an exception.
3. Load the fluid-pr-guide skill NOW (via the Skill tool) before composing anything. It contains the title conventions, body template, and section guidance you need. Do NOT skip this step or rely on memory.
4. Using the loaded fluid-pr-guide, compose the PR title and body following its conventions and template.
5. Print the proposed title and body as text, then immediately use the ask_user tool to let the user choose what to do next. Use these exact options:
   • "Create PR" — Push the branch and open the pull request
   • "Create draft PR" — Push the branch and open a draft pull request
   • "Edit" — Revise the title or body before creating
   • "Cancel" — Don't create a PR
6. If the user picks "Edit", apply their edits and re-present (go back to step 5). If "Create PR" or "Create draft PR", push and create accordingly. If "Cancel", stop.

Pushing and Creating the PR

Before pushing, verify that origin does not point to microsoft/FluidFramework. Run:

git remote get-url origin

If the URL contains microsoft/FluidFramework, stop unless the branch is prefixed with test/ and the conversation context or changed files indicate that the change needs Azure Pipelines testing. A user request for a "test branch" in that context is sufficient intent to use the exception. Otherwise, tell the user they should push to their fork instead and do not proceed.

Once the checks in steps 1–2 pass silently, compose the title and body, print them as text, then use the ask_user tool with the four options as described in step 5. This is the only point where the fluid-pr flow asks the user a question.

# Push branch (first time)
git push -u origin <feature-branch>

# Create PR (option 1)
gh pr create \
  --title "<title>" \
  --body "$(cat <<'EOF'
<body>
EOF
)"

# Create draft PR (option 2) — add the --draft flag
gh pr create \
  --draft \
  --title "<title>" \
  --body "$(cat <<'EOF'
<body>
EOF
)"

After creating the PR, output the PR URL so the user can navigate to it.

Updating an existing PR description

When asked to update an existing PR's title or body, use gh pr edit to apply the changes directly.

Specify --repo <owner/repo> to avoid ambiguity between forks and upstream.

For a description update, write the new body to a temp file, then apply it to the PR:

cat <<'EOF' > "$TMPDIR/pr-body.md"
<new body content>
EOF
gh pr edit <number> --repo <owner/repo> --body-file "$TMPDIR/pr-body.md"

To update the title, use gh pr edit <number> --repo <owner/repo> --title "<new title>". After updating, output the PR URL.