Mark Stacey 20b2c5f004 Fix LavaMoat config check (#10514) ... The CI script to ensure no LavaMoat policy changes are required has been failing despite there being no changes. It turns out that the command used to check for changes (`git diff-index`) was failing despite the lack of changes because the file was written again by `yarn lavamoat:auto` but git hadn't gotten around to updating its index since the write occurred, so it was considering it as changed until it verified it wasn't [1]. The command has been replaced by `git diff --exit-code --quiet`, which should do exactly the same thing except that it forces git to update its internal cache to verify whether changes are present. [1]: https://stackoverflow.com/questions/34807971/why-does-git-diff-index-head-result-change-for-touched-files-after-git-diff-or-g		2021-02-25 11:13:47 -03:30
..
chrome-install.sh
create-lavamoat-viz.sh
deps-install.sh
firefox-install.sh
firefox.cfg
release-bump-changelog-version.sh
release-bump-manifest-version.sh
release-create-gh-release.sh
release-create-master-pr.sh
release-create-release-pr.sh
show-changelog.awk
test-run-e2e.sh
validate-allow-scripts.sh
validate-lavamoat-policy.sh
yarn-audit.sh