We recommend throughout the Stack docs to always use an actual commit SHA for the commit field in repos. However, nothing enforces this, and (at least in the case of Git) it's possible to use any tree-ish. With lock files, it would make sense to ensure that we always lock to a specific commit SHA, regardless of what value is put in commit field.
Taking this one step farther: I think it would be possible to make the commit field entirely optional, which would have the semantics of cloning the default branch, finding the SHA of HEAD, and including that in the lock file.
We recommend throughout the Stack docs to always use an actual commit SHA for the
commit
field in repos. However, nothing enforces this, and (at least in the case of Git) it's possible to use any tree-ish. With lock files, it would make sense to ensure that we always lock to a specific commit SHA, regardless of what value is put incommit
field.Taking this one step farther: I think it would be possible to make the
commit
field entirely optional, which would have the semantics of cloning the default branch, finding the SHA of HEAD, and including that in the lock file.