Calculate and record uncommittedHash when creating a build

[ghengeveld]

This is required for the "is outdated" concept in the Visual Tests addon, but may also be used in the future for other builds (e.g. during onboarding or even CI builds with an unclean working directory).

[linear]

AP-3369 Add concept of outdated builds

• Store a "git changes" hash as well as the commit hash on the build (ideally in the index, but it could be locally).
  • The CLI could understand the concept of a "uncommitted builds" also.
• Poll git for the current commit hash + changes hash (we also need to poll for branch for AP-3366 eventually)
• Consider snapshots out of date if the two don't match.

To get a hash of staged+unstaged+untracked changes:

(
 git diff --name-only --diff-filter=d --cached; 
 git diff --name-only --diff-filter=d; 
 git ls-files --others --exclude-standard
) | git hash-object --stdin-paths | git hash-object --stdin

This seems to be the only way to get a full hash of all these types of changes, whilst excluding any deleted files (which would cause an error because they can't be hashed).

[weeksling]

lgtm!

[weeksling]

It looks like this is failing tests because the CI for multiple reasons. Action-canary is a git.email issue others are 400 errors from git

[ghengeveld]

It looks like this is failing tests because the CI for multiple reasons. Action-canary is a git.email issue others are 400 errors from git

That's caused by this PR which is released as canary but not merged yet. It needs to deal with missing email config.

The unit tests fail due to missing mock for getUncommittedHash. I added those just now.

The other tests fail because the index doesn't accept uncommittedHash yet, which will be resolved when merging this PR.