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

New option: remote #43

Open
jugglinmike opened this issue Apr 9, 2015 · 4 comments
Open

New option: remote #43

jugglinmike opened this issue Apr 9, 2015 · 4 comments

Comments

@jugglinmike
Copy link

I'd like to push to a repository that is not my "origin" remote. This plugin exposes an option named "repo" that allows me to specify any URL, but I would like to limit duplication by instead specifying the remote's name (which I have already registered within the repository).

The discussion in gh-15 includes references to a "remote" option. This sounds like it might be relevant, but there is currently no documentation for it.

@tschaub
Copy link
Owner

tschaub commented Apr 9, 2015

The option is still there, but the docs were causing confusion. See f749b7c. If you can use clone and remote to do what you want, I'd accept a pull request that brought back the documentation.

@jugglinmike
Copy link
Author

Since the remote option relies on the clone option, and the clone option is intended to be a full git URL, I think the current implementation is incompatible with my goal (to avoid duplicating configuration data). If this is true, it would take a backwards-breaking API change to address.

@tschaub
Copy link
Owner

tschaub commented Apr 9, 2015

The clone option is a path to an existing clone. The repo option is the URL for a remote repository.

You should never use the remote option together with clone. But I'm pretty sure that using remote together with clone is what you are looking for.

Yes, the short option names are confusing.

@jugglinmike
Copy link
Author

Here's my understanding: The newly-cloned repository created by the plugin will not be have the configuration of the repository I am using directly. So even though when I run

$ git remote add upstream git://some-url.git

...I can verify with

$ git config --get remote.upstream.url

...this information will not be available from the new "clone" repository created by this Grunt task.

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

No branches or pull requests

2 participants