Errors in project metadata gathering causing build failures

[jmhobbs]

Unintentionally, the steps to gather project metadata were causing builds to fail if there was an error.
As this data is not required, we should not fail the whole process if one of these fail.

This appears to be the original intention (with existing try/catch) but async returns bypassed them.

Additionally, the timeout on getCommittedFileCount was reduced, as an up to 20s slowdown for non-critical information was too high.

📦 Published PR as canary version: 11.20.3--canary.1131.12283964969.0

✨ Test out this PR locally via:

npm install [email protected]
# or 
yarn add [email protected]

[github-actions]

📦 Package Size: 5448 KB

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 80f85041	✅ 86.67% (target: 80.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (80f8504)	Report Missing	Report Missing	Report Missing
Head commit (9f23eea)	7304	5031	68.88%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1131)	15	13	86.67%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[chromatic-ci-bot]

🚀 PR was released in v11.20.2 🚀