Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Hi, > > On Mon, 2 Aug 2021, Atharva Raykar wrote: > >> [...] > > You can use the `linux-gcc` job for that, imitating how b2627cc3d4b (ci: > include the built-in `git add -i` in the `linux-gcc` job, 2020-01-14) did > it for the built-in `git add --interactive`: > > ci: include the built-in `git add -i` in the `linux-gcc` job > > This job runs the test suite twice, once in regular mode, and once > with a whole slew of `GIT_TEST_*` variables set. > > Now that the built-in version of `git add --interactive` is > feature-complete, let's also throw `GIT_TEST_ADD_I_USE_BUILTIN` into > that fray. > > Signed-off-by: Johannes Schindelin <johannes.schindelin@xxxxxx> > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > > diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh > index ff0ef7f08e7..4df54c4efea 100755 > --- a/ci/run-build-and-tests.sh > +++ b/ci/run-build-and-tests.sh > @@ -20,6 +20,7 @@ linux-gcc) > export GIT_TEST_OE_DELTA_SIZE=5 > export GIT_TEST_COMMIT_GRAPH=1 > export GIT_TEST_MULTI_PACK_INDEX=1 > + export GIT_TEST_ADD_I_USE_BUILTIN=1 > make test > ;; > linux-gcc-4.8) Thanks, this is helpful!
