This seems to be the only part of the code that doesn't expect a relative path to the current working directory, and that's a quirk of git rev-parse with a revision specified. (Without HEAD, this would also work.)
This change ensures we are always looking at files in the current directory so deployment files do not have to be located in the root of a repository.
This seems to be the only part of the code that doesn't expect a relative path to the current working directory, and that's a quirk of
git rev-parse
with a revision specified. (Without HEAD, this would also work.)This change ensures we are always looking at files in the current directory so deployment files do not have to be located in the root of a repository.
I have:
develop
branchhlint .
(lint found code you did not write can be left alone)$(nix-build -A selftest --no-out-link)
nix-build release.nix -A build.x86_64-linux --no-out-link
(orx86_64-darwin
on macOS)