Updating wrong repo when deploying same repo multiple times with different branches

[ADRFranklin]

I am experiencing an issue, where pico seems to be updating the wrong repo when using branches.

It seems pico is able to correctly perform an update on the first start, but then after it continues to update the wrong branch (it calls the up event) and the service is restarted.

I think a test needs to be performed which pulls from the same repo, and has 2 different branches being used on it. This should make it clear what the problem is.

[ADRFranklin]

I have also noticed that it is passing the env variables to the wrong repo too, not just updating the wrong repo.

[Southclaws]

I can't reproduce this. Is this specifically happening when you have multiple targets pointing at the same repository?

[ADRFranklin]

Yes, this happens only when I have 2 instances of the same repo.

[Southclaws]

This might be a gitwatch issue then, two identical repos is undefined behaviour.

I think the solution would be to suffix the directory name with the branch name, separated by a _.