Build Dashboard Errors

[jmayclin]

Problem:

Problem 1 - dead dependencies
Our build dashboard has a transitive dependency on node 12 through ethomson/issue-dashboard. Node 12 is now deprecated, and is causing CI runs of the build dashboard action to fail. (just a warning, not an error)[but we should still fix it] An example is here

Problem 2 - flaky behavior
I'm not certain how this was caused, but the tree seems to be in an inconsistent state, which caused a failure when trying to push changes to the branch: here It seems like this might be related to a race condition between the doxygen update action and the build dashboard action.

This problem is irritating because it ends up marking closed PRs as "bad" PR's since they fail the build-dashboard ci, but the CI only runs after the action is closed/merged, so there isn't an easy way to prevent this.

Solution:

I generally don't want any actions that run after I merge the PR, that way I can be 100% sure that the merge is good and will be documented as such.

Option 1 (preferred): nuke this entire action, the issue-dashboard repo appears to be dead, find some other alternative (and preferably don't run it on PR closes)

Option 2:

• git pull on the gh-page branch actions to prevent the inconsistent state.
• shift the action to a schedule expression to de-couple it from PR's. It could run every day at midnight or something like that.

Requirements / Acceptance Criteria:

No action failures, and preferably a replacement

[dougch]

Both the dashboard and doxygen actions run on PR close, which seems to be causing a race condition, e.g. https://github.com/aws/s2n-tls/actions/runs/3943198717/jobs/6747759539. Maybe it's not a safe to assume only one update to gh-pages is in-flight at any time?