Carlo Arenas <carenas@xxxxxxxxx> writes:
> It won't, because it is running with sudo ;). note that as stated in
> the commit message, this requires a fairly open sudo setup (like the
> one github provides with their actions).
Ahh, OK. So this is pretty much only for CI environment and such,
not on a typical developer and end-user box.
OK, but the potential issues that I raised about cleansed
environment, not limited to $PATH, still exists. Perhaps
the prereq check can be tightened to something like:
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=no-no-name \
PATH=no-such-path:$PATH \
sudo sh -c "echo '\$PATH \$GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME'" |
grep "^no-such-path.* no-no-name$"
i.e. we export an envionment with a known value that is unlikely
value for the variable in tester's environment, prepend a known
string that unlikely begins the tester's $PATH, and ask sudo what
values, if any, the process sudo spawned sees in these two
environment variables. An environment that does not molest PATH and
passes environment variables we set in the tests to affect execution
of "git" being tested will pass the above test. Otherwise the
environment would silently be breaking our expectation.
