Krate Pull Request Lifecycle overview

The full lifecycle of a pull request within Krate's Kubernetes-native forge, from creation through merge. Steps: 1. PR creation: A PullRequest aggregated API resource is created (via UI, kubectl, or git push with a create-pr flag). Krate syncs the underlying Git branches with Gitea. 2. CI pipeline trigger: BranchProtection rules on the target branch trigger a Pipeline resource. PipelineRuns execute as Kubernetes Jobs — lint, test, build, security scan. 3. Review assignment: Reviewers are assigned based on CODEOWNERS patterns or team routing rules. Reviewers submit PullRequestReview resources with approve/request-changes verdicts. 4. Status conditions: The PR aggregates status from CI checks, review approvals, and policy evaluations into Kubernetes-style status conditions. The merge button is unlocked when all required conditions are True. 5. Agent dispatch (optional): Reviewers or authors can dispatch an agent via /agent comment to address review feedback automatically. 6. Merge: Merge strategy (merge/squash/rebase) is applied per BranchProtection. Post-merge hooks trigger downstream pipelines, release creation, and issue auto-close.