Is this a rust rewrite of loop and meta 👀? thats exciting!
I'm still curious if you have any plans around deterministic checkouts. mateodelnorte/meta#329
Git has mutable history, so deterministic checkouts can't be entirely guaranteed outside monorepos unfortunately... Perhaps if commit hash, branch, and date are added to the .meta project entries a checkout can use the nearest commit (probably prioritizing down stream commits) if the hash is missing and throw a warning or an error if the branch or merge commit(s) are absent.
Good APIs and versioning can reduce the need for this, but I still think it has value for debugging, reproduction, communication, and transparency.
Is this a rust rewrite of loop and meta 👀? thats exciting!
I'm still curious if you have any plans around deterministic checkouts. mateodelnorte/meta#329
Git has mutable history, so deterministic checkouts can't be entirely guaranteed outside monorepos unfortunately... Perhaps if commit hash, branch, and date are added to the
.metaproject entries a checkout can use the nearest commit (probably prioritizing down stream commits) if the hash is missing and throw a warning or an error if the branch or merge commit(s) are absent.Good APIs and versioning can reduce the need for this, but I still think it has value for debugging, reproduction, communication, and transparency.