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
Let's say we have a remote repository https://github.com/user/repo.git and it wasn't added to local git remote list. The following code should create the repository if 'git ls-remote' fails
Bit if the public key is set correctly, running 'git ls-remote [email protected]:user/repo.git' doesn't cause an exception and, later, the code fails because the repo po_translator doesn't exist.
The text was updated successfully, but these errors were encountered:
What do you think about this?
I can see problem when someone change git_repository in config, should we check if it's still the same? But probably it's not common case.
I ran into this problem using django-c3po so I'll give my opinion from that perspective. Since django-c3po has a setting GIT_REPOSITORY that's used when calling git_push, I think users expect THAT repository to be used. I'm guessing django-c3po users have no idea what exactly git_push does, shouldn't be bothered with git configuration beyond settings and C3PO should override .git/config since it added it in the first place so "remote show" line should be evicted entirely. Could you please review #3 ?
Let's say we have a remote repository https://github.com/user/repo.git and it wasn't added to local git remote list. The following code should create the repository if 'git ls-remote' fails
Bit if the public key is set correctly, running 'git ls-remote [email protected]:user/repo.git' doesn't cause an exception and, later, the code fails because the repo po_translator doesn't exist.
The text was updated successfully, but these errors were encountered: