You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0f2649c
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(source-control): pull request behaviour comes from forge capabilities
The pull request service, orchestration, contracts and agent prompts still
decided forge behaviour by name: the watch waited for missing checks only when
the provider was "github", the sync reactor matched only `gh pr` and `glab mr`
merge commands, routing identity was typed and checked as the "github"
literal, contracts carried every forge's install and sign-in text, the generic
listing held GitHub's search-index workaround, and the Code tab collapsed
every review comment range to one line because only GitHub could carry one,
so no host got ranged comments.
Forges now declare these. Pull request capabilities gain checksAlwaysReport
(GitHub) and review.rangeComment (GitHub); providers gain
unavailableRequirement (each forge's own text) and
listsAcrossMayOmitRepositories (GitHub); client definitions gain
changeRequestCloseCommand (gh pr merge|close and gh stack merge, glab mr,
cafe pr|stack, tea pr|pulls and fj pr, az repos pr update --status
completed|abandoned; Bitbucket has no CLI). The service puts the requirement
on PullRequestUnavailableError.requirement, returns the provider's kind from
routingIdentity, and the client routes when the source server answers and the
alternate names the same kind. Review comment drafts gain an optional
startPosition, which GitHub sends as start_line/start_side; the Code tab and
the guide excerpts keep a selection's first line within one hunk when the
host supports it. Agent-facing text and the agent-credit setting no longer
name GitHub.
Compatibility: every new field is optional. A new client reading an old
server gets no requirement (generic message, as for GitCafe today), no
rangeComment (one-line comments as before) and a "github" routing identity,
which is still a kind. An old client reading a new server ignores the new
fields; its unavailable messages fall back to its generic text, and a routing
identity of another kind (none exists yet) would fail to decode and skip
routing.
Behaviour changes: GitHub review comments can span lines. A run that merges
or closes with cafe, tea, fj or az refreshes its links at once. A host
without listsAcrossMayOmitRepositories believes its cross-repository read's
silence (only GitHub implements that read today).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
subtitle="Remove recognized agent credits from GitHub merge and squash messages, keeping human co-authors. Includes auto-merge. Excludes merge queues, stack merges, and existing commits."
371
+
subtitle="Remove recognized agent credits from merge and squash messages on hosts that support it, keeping human co-authors. Includes auto-merge. Excludes merge queues, stack merges, and existing commits."
"The pull request's web URL, for example https://github.com/owner/repo/pull/123. Preferred when you have it; host, repository and number are read from it.",
46
+
"The pull request's web URL as its host shows it, for example https://git.example.com/owner/repo/pull/123 or https://git.example.com/group/project/-/merge_requests/123. Preferred when you have it; host, repository and number are read from it.",
0 commit comments