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
dahlbyk/posh-git#326 added support for Gone branch status, which is missing from this cache response. I'd suggest a boolean UpstreamGone property.
To reproduce (assuming origin/gone doesn't exist):
> git branch gone
> git config branch.gone.remote origin
> git config branch.gone.merge refs/heads/gone
> git checkout gone
Switched to branch 'gone'
Your branch is based on 'origin/gone', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
The text was updated successfully, but these errors were encountered:
Note (mostly for myself):
If origin does not exist, above repro will not cause git to report the branch being gone; origin (but not origin/gone) must exist.
Report UpstreamGone. Resolves#19.
UpstreamGone is set when a branch has no remote tracking reference but still has an upstream configured. This is similar to the git warning:
Your branch is based on 'origin/master', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
dahlbyk/posh-git#326 added support for Gone branch status, which is missing from this cache response. I'd suggest a boolean
UpstreamGone
property.To reproduce (assuming origin/gone doesn't exist):
The text was updated successfully, but these errors were encountered: