Manage multiple remotes

[AlexandreMary]

Is your feature request related to a problem? Please describe.

The "downloading" of repositories fails when the target repo already exists with an "origin" remote that differs from the one required in the bundle.

Describe the solution you'd like

Do not rely solely on "origin", but name the remotes uniquely (using a hash of the url?) and fetch/checkout from the required remote ?

That's what I implemented in a package wrapping ecbundle, but under certain conditions it still fails, so I would rather it to be implemented directly in ecbundle.

Describe alternatives you've considered

No response

Additional context

No response

Organisation

No response

[wdeconinck]

Hi Alexandre,

In early version of ecbundle there was no remote called "origin", and rather a username or organisation name was used that was introspected from the git address.
There was then pushback on this as well because not every repository would have the same "origin" as a default name.
So then I added the extra bundle option to name the remote, but the default is still "origin".

An example bundle file could be:

---
### Bundle

name    : mybundle

projects :
    - project1 :
        git     : ${BITBUCKET}/user/project1
        remote  : ec-user
        version : 0.0.1

Here the initialised remote will be called "ec-user".

Is this what you had in mind?

[AlexandreMary]

I didn't know about this option, I will try to see if it can bypass my current issue.
But in my mind ecbundle could look in the remotes if the URL requested exists, and if so, take the according "remote".
E.g if bundle is:

projects :
    - project1 :
        git     : ${BITBUCKET}/user/project1
        version : 0.0.1

and in the repo you have

ec-user	${BITBUCKET}/user/project1 (fetch)
ec-user	${BITBUCKET}/user/project1 (push)
origin	https://github.com/ACCORD-NWP/project1 (fetch)
origin	https://github.com/ACCORD-NWP/project1 (push)

then ecbundle would fetch/checkout from ec-user instead of origin
But if you have e.g.
git : ~rm9/my/local/project1 in the bundle, i.e. a "new" remote,
ecbundle would
git remote add <new_remote> ~rm9/my/local/project1
where <new_remote> could be a short hash of ~rm9/my/local/project1 if not specified as attribute remote in the bundle

What do you think ?

[AlexandreMary]

I have submitted PR #40 in which I propose an implementation of the solution I was talking about.

[wdeconinck]

This is now merged. Thanks for submitting the PR!