-
-
Notifications
You must be signed in to change notification settings - Fork 934
GitPython reports no remote 'origin' #910
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
Comments
Thanks for posting! I am tentatively acknowledging the issue based on the assumption that certain In order to fix the issue, one would have to provide an example making the issue reproducible. Usually refs are stored in the
I suspect the |
Hey @Byron, a fresh clone of the repositories in question fixed the issue so I can't get you a |
Hi @Byron .. I followed your suggestions. My project is as follow: $ grep -r origin .git
.git/refs/remotes/origin/HEAD:ref: refs/remotes/origin/master
.git/config:[remote "origin"]
.git/config: fetch = +refs/heads/*:refs/remotes/origin/*
.git/config: remote = origin
.git/config: remote = origin
.git/packed-refs:510b2bcc03c4b33ee976001fc347e48c50fc953c refs/remotes/origin/Desarrollo-CI
.git/packed-refs:2e2fdce01e7d1809ec20de7ecef2f1327eef3493 refs/remotes/origin/master
.git/packed-refs:e7cad3b1378790fe20c2ac9c1fb22e3c66f81e18 refs/remotes/origin/monitoreo
.git/packed-refs:1869a38e0b7495586067f2fa65d50f6dd6f03f93 refs/remotes/origin/refactor I commented the problem before in another issue readme. Is the same issue, and my project isn't working yet Regards |
Thanks, @panterozo . |
As part of spring cleaning, I am closing this issue as it was opened more than half a year ago while still asking for feedback. If this is a mistake or any other action should rather be taken, please let me know in the comments or create a new issue as digest of this one. |
Hi,
I've been seeing the following error pop up every now and then. GitPython
3.0.0
fails to identify the remoteorigin
even though it is there.The stacktrace shows the following:
I don't exactly know why this happens. But a few of our repositories get into this state on occasion. We're running on Python 3.6 @ CentOS 7.
Thanks!
The text was updated successfully, but these errors were encountered: