As discussed on https://radicle.zulipchat.com/#narrow/stream/438104-nix/topic/version.20of.20git/near/440313515, the tests failed with git 2.34 (in an ubuntu:22.04 container) with:
--- Expected
++++ actual: stdout
1 - branch 'master' set up to track 'origin/master'.
1 + Branch 'master' set up to track remote branch 'master' from 'origin'.
Exit status: 0
As per @fintohaps’ suggestion, this gets the tests passing again on git 2.34.
As discussed on https://radicle.zulipchat.com/#narrow/stream/438104-nix/topic/version.20of.20git/near/440313515, the tests failed with git 2.34 (in an ubuntu:22.04 container) with:
--- Expected
++++ actual: stdout
1 - branch 'master' set up to track 'origin/master'.
1 + Branch 'master' set up to track remote branch 'master' from 'origin'.
Exit status: 0
As per @fintohaps’ suggestion, this gets the tests passing again on git 2.34.
Excellent change, could not have done it better myself
Is it possible to do prefix matching with ...? Then this would allow:
...'master' set up to track...
Is it possible to do case-insensitive or regex-based matching? Then this would allow:
[Bb]ranch 'master' set up to track...
Is it possible to do prefix matching with
...? Then this would allow:...'master' set up to track...Is it possible to do case-insensitive or regex-based matching? Then this would allow:
[Bb]ranch 'master' set up to track...
I thought about something like this, but I don’t really see the benefit since we don’t really mind what Git says here. All that matters is that the command succeeded.
Aye, forget about my nitpicking then.
Rebase.