The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

lgtm ACK d66efa3

Just checking if I get this right: git rev-parse HEAD:foo uses the contents of foo as fingerprint (instead of the revision in which it was touched last)?

Yeah, it is probably even more correct, as it doesn't commit to irrelevant stuff such as the commit message. So the fingerprint hash will be different, however, the important part is that the output should commit to the content of the depends system.

git log -1 ./depends, git rev-list -1 HEAD ./depends, git rev-parse HEAD:depends, and git ls-tree HEAD ./depends should all have this property.

Yeah, it is probably even more correct, as it doesn't commit to irrelevant stuff such as the commit message. So the fingerprint hash will be different, however, the important part is that the output should commit to the content of the depends system.

git log -1 ./depends, git rev-list -1 HEAD ./depends, git rev-parse HEAD:depends, and git ls-tree HEAD ./depends should all have this property.

A shallow repo, which is used in the CI, lacks details. Therefore, only git rev-parse HEAD:depends and git ls-tree HEAD ./depends are suitable as they return the same output for both deep and shallow repos.