Files
computer-playbook/docs/agents/action/pull-request.md
kevinveenbirkenbach b984715627 docs(agents): clarify push/PR flow, target repo, run-id resolve
- pull-request.md: PRs must target canonical repo behind s.infinito.nexus/code; agent resolves redirect and compares against origin.
- push-trigger-pull.md: freeze <branch> once (propose current and wait if unnamed); forbid checkout/switch; handle non-fast-forward; fetch before diff; define distro-specific scope; capture <prev-run-id> to avoid stale-run watch; resolve <pr-number> via isDraft dispatch; null-guard.
- cheatsheet.md: push-trigger-pull prompt takes explicit <branch> placeholder.
2026-04-17 22:52:49 +02:00

8 lines
959 B
Markdown

# Pull Requests
- You MUST choose the matching Pull Request template before you write a PR description.
- You MUST follow the template selection guidance in [CONTRIBUTING.md](../../../CONTRIBUTING.md).
- You MUST use the templates from [PULL_REQUEST_TEMPLATE](../../../.github/PULL_REQUEST_TEMPLATE).
- You MUST treat the selected template as the SPOT for PR structure, author input, and review context.
- PRs MUST target the canonical repository that <https://s.infinito.nexus/code> redirects to, unless the operator explicitly names a different target. Before creating the PR, the agent MUST resolve the redirect (e.g. `curl -sSIL https://s.infinito.nexus/code | grep -i '^location:'`) to obtain the canonical repository URL, then compare it against `git remote get-url origin`. If the two do not point to the same repository (host + owner + repo, ignoring `.git` suffix and `https://` vs. `git@` scheme), stop and ask the operator before creating the PR.