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 21683f2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(vcs): fast-forward a local pull request branch the host left behind
Without `force`, Bitbucket, Forgejo and GitCafe check out an existing
pull request branch as it was, so a branch behind the pull request
stayed there. After the provider checkout, the branch now moves to the
provider's head commit through the same clean, fast-forward-only
refresh reused worktrees use; diverged or dirty checkouts stay put and
report that they are not on the head.
The warning now says the checkout could not be confirmed on the latest
commit rather than asserting that its code differs, since a provider
that reports no head commit also lands there.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* Shown in place of success when a checkout is kept where it was rather than on the pull
3
-
* request's head, by both the pull request panel and the branch picker's checkout dialog.
2
+
* Shown in place of success when a checkout is not confirmed on the pull request's head, by both
3
+
* the pull request panel and the branch picker's checkout dialog.
4
4
*/
5
5
exportconstOFF_HEAD_PULL_REQUEST_CHECKOUT_TOAST={
6
6
type: "warning",
7
-
title: "Checked out, but not on the pull request's commit",
7
+
title: "Checked out, but not confirmed on the latest commit",
8
8
description:
9
-
"The checkout is not on the pull request's latest commit, so the code there differs from the pull request. Uncommitted work or local commits keep it where it is.",
9
+
"This checkout could not be confirmed at the pull request's latest commit, so its code may differ. Local commits or uncommitted work keep a checkout where it is.",
0 commit comments