-
Notifications
You must be signed in to change notification settings - Fork 89
Hard coded remote names #141
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
That would be an amazing nice to have feature, indeed! And I'm totally open for getting a PR to get something doing that implemented. I believe that could be done with a command like:
because I'd rather avoid doing it automagically whenever you call any command (when I call
And anyway, until it's done, you can easily add the gitlab remote when it's missing with:
Currently, I first want to get the basic features well covered, and the existing one to work well. |
I've pushed |
First anniversary release 🎂 This release marks the first anniversary and 10th release of git-repo 🎉 Now git-repo supports 6 git services: github, gitlab, bitbucket, gogs, gitea and gitbucket It supports the following commands: clone, fork, create, delete, add, open, ls, request, gist And it's becoming relatively stable (keep sending bug reports 🙏) ♥ Contributors Thanks to @kounoike for the gitbucket support 🙌 Now there are three contributors promoted to collaborators: * @kounoike, @pyhedgehog and @Crazybus 🚧 Features * When add has no parameters, add default remote #100 #141 * When add has 'upstream' parameter, add the upstream remote #99 #141 * Use default branch instead of hardcoded 'master' #91 * Refactor and complete bitbucket support #43 #11 #80 #14 #89 #90 #79 * Loosen versions of dependencies #133 * Report if the service is already setup #136 * Adds GitBucket support #142 #144 * Adds support for ssh:// URL #148 🚒 Bugfixes * fix various crashes #152 * fix gitlab clone crash #129 * fix request create command #147 #127 * fix request fetch command #138 #131 * fix wizard crash #149 * fix mishandling of renamed gitlab project urls #137 📝 Documentation * documentation #145 Signed-off-by: Guyzmo <[email protected]>
I've only started playing, and it seems like the remote 'gitlab' is special, and everything else is ignored. I suspect the same occurs for github and others.
This means
git-repo
cant be immediately used in a git clone of a gitlab repo that was cloned usinggit clone
, as that will use the remote nameorigin
.It would be nice if
git-repo
handled a missinggitlab
remote by looking for another suitable remote that points to gitlab, with a sensible strategy that works in most cases.The most obvious fallback is to look to see if
origin
is a gitlab repo, and use that.Then looking at all remotes, and see if there is only one that points to gitlab, then that should be the default used.
git-repo
could then create agitlab
remote if it needs to avoid expensive calls again, so thegitlab
remote becomes more of a cached default remote, rather than the only one that works.The text was updated successfully, but these errors were encountered: