Re: Push force-with-lease with multi-URL remote

that blocks port 22 outbound, so I always just use SSH. But I realize other people’s experience varies. -- Christopher Head

Re: Push force-with-lease with multi-URL remote

ng due to having to remember to push to all of them. If I understand what remote groups are (separate remotes but you can act on all of them with one command?) then they should be perfect. However it does not look like they work for pushing. Would it make sense to add? -- Christopher Head

Re: Push force-with-lease with multi-URL remote

On July 27, 2019 10:46:43 AM PDT, Junio C Hamano wrote: >Christopher Head writes: > >Quite honestly, the true culprit of the above story is that you are >letting multiple logically different remote repositories [*1*] use >the same single remote-tracking refes/remotes/myremote/ h

Push force-with-lease with multi-URL remote

CAS operations in 3a succeeded, change refs/remotes/myremote/mybranch to X. Thoughts? Does anyone have a use case for the existing behaviour? I have attached a shell script which constructs some repos and demonstrates the situation. Thanks! -- Christopher Head test Description: Binary data