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
error Cannot find the remote origin url #1
Comments
What's the output of |
On Mon, Feb 9, 2015 at 6:11 PM, Ionică Bizău notifications@github.com
No output at all. I don't have any remotes as you cannot push with a Thanks, |
OK, so you have to add one. What do you mean by
|
This is git-svn: http://git-scm.com/docs/git-svn Thanks, On Mon, Feb 9, 2015 at 6:15 PM, Ionică Bizău notifications@github.com
|
I have this tho:
Regardless, relying on remote urls seems unnecessary, commits already have a good id: the hash - why can't you compare just on that? |
Is there a way to get the the url only? In the future I will probably make some stats regarding the repositories too. In the meantime you can add a dummy remote url: git remote add origin git@dummy.com:dummy/dummy.git |
Aha! Perhaps git-stats-importer can use something like |
@philadams 👍 Can you create a pull request with this? Also, would it solve the issue with |
I reproduce this bug on windows, on a pure git (pure, not bare) repository.
|
Hmm... interesting. What about the following? $ git config --get remote.`git remote | head -n1`.url |
Same error message
|
@nilleb What about |
@IonicaBizau Yes - but I see you beat me to it! 👍 I confirm it's working just fine as importing in my repos now - thank you! |
splitting the instruction in two distinct instructions works. |
How should do we define the default remote? |
+1 |
@nilleb @IonicaBizau I hadn't considered that. What exactly is the remote being used for? Just the |
@philadams In git-stats |
Nice - anticipating your future work with excitement. Love this project - thank you! |
Thank you, @philadams, for nice words! 😄
See #26 for more information. |
Seems it doesn't work on my git-svn repo 😞
The text was updated successfully, but these errors were encountered: