Paul Gschwendtner 17a95dac22 build: resolve benchmark compare SHA from PR branch or upstream remote (#50764) ... If we try to resolve the benchmark compare ref (which may be just `main`), we are just looking inside the PR branch- but that may not include the `main` SHA. i.e. it's possible to run a comparison where the PR is slightly behind of the `main` branch, or a comparison commit from a different branch is used. We fix this/ and simplify the logic by resolving the SHAs directly in the TypeScript code, instead of relying on the rather brittle Bash. Note that current solution still works, but we sometimes may not be able to resolve to an actual SHA- causing issues as in 864bd72cb2 PR Close #50764		2023-06-19 12:54:54 +00:00
..
benchmarks	build: resolve benchmark compare SHA from PR branch or upstream remote (#50764)	2023-06-19 12:54:54 +00:00
build	build: continue publishing @angular/bazel snapshot builds (#49583)	2023-03-24 10:35:31 -07:00
ci	build: remove unused script from removed components CI job (#50429)	2023-05-23 17:18:27 +00:00
test	build: start only the minimum number of Saucelabs browsers required (#50393)	2023-05-23 14:12:28 +00:00
compare-main-to-patch.js	build: clean up references to old master branch (#45856)	2022-05-04 16:23:33 -07:00
tsconfig.json	build: convert release package build scripts to typescript (#46456)	2022-06-22 14:35:31 -07:00