Fix deploying the TS migration dashboard
Explanation
When the TypeScript migration dashboard is updated, it is built and deployed in another repo, which is then deployed via GitHub Pages. To push to this repo we have to set a Git username and email. This is missing from the CircleCI config, so this commit uses the metamaskbot GitHub account to do that.
More Information
See the PR introducing the TypeScript migration dashboard for more context.
Also see Storybook, which takes a similar approach.
Manual Testing Steps
There isn't anything to test here, but the job-publish-ts-migration-dashboard step in CircleCI should not fail. This step will only get run when this PR is merged, so a subsequent PR will be needed if this one doesn't fix it.
Pre-Merge Checklist
- [ ] PR template is filled out
- [ ] IF this PR fixes a bug, a test that would have caught the bug has been added
- [ ] PR is linked to the appropriate GitHub issue
- [ ] PR has been added to the appropriate release Milestone
+ If there are functional changes:
- [ ] Manual testing complete & passed
- [ ] "Extension QA Board" label has been applied
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.
Builds ready [8037531]
- builds: chrome, firefox, opera
- builds (beta): chrome, firefox, opera
- builds (flask): chrome, firefox, opera
- build viz: Build System
- mv3: Background Module Init Stats
- mv3: UI Init Stats
- mv3: Module Load Stats
- mv3: Bundle Size Stats
- code coverage: Report
- storybook: Storybook
- typescript migration: Dashboard
- all artifacts
Page Load Metrics (1812 ± 61 ms)
| Platform | Page | Metric | Min (ms) | Max (ms) | Average (ms) | StandardDeviation (ms) | MarginOfError (ms) |
|---|---|---|---|---|---|---|---|
| Chrome | Home | firstPaint | 87 | 1896 | 199 | 389 | 187 |
| domContentLoaded | 1649 | 2122 | 1789 | 127 | 61 | ||
| load | 1649 | 2122 | 1812 | 126 | 61 | ||
| domInteractive | 1649 | 2122 | 1789 | 127 | 61 |