Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream Gone #19

Closed
dahlbyk opened this issue Jan 15, 2017 · 1 comment · Fixed by #20
Closed

Upstream Gone #19

dahlbyk opened this issue Jan 15, 2017 · 1 comment · Fixed by #20

Comments

@dahlbyk
Copy link

dahlbyk commented Jan 15, 2017

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)
@cmarcusreid
Copy link
Owner

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.

cmarcusreid added a commit that referenced this issue Jan 17, 2017
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants