Improve Workflow Orchestration

[GuyHoozdis]

Some workflows, like the tests, will trigger on a merge and then again on the release tag. It seems wasteful and unnecessary if the workflow already passed on the merge prior to tag/release.

• Can I stop running workflows if newer ones are triggered?
• Can I chain workflows together?

Events that trigger workflows

• workflow_run
• workflow_dispatch
• workflow_call

[GuyHoozdis]

1. I think the upload to codecov.io should only be from permanent branches - main is the only one for this repo.
2. For PRs to pass the required coverage should be verified. Does it need to be done again after the merge?
3. Are the actions in PRs running against the changeset on the branch, only, or on the changeset that would result from the merge with the branch the PR is targeting?
4. If I'm requiring 100% coverage, is there any way for the PR to be passing, but then failing after the PR is merged? It is possible when requiring less than 100%.
5. Here are some examples of different ways be more focused with the triggering events.

[GuyHoozdis]

Here are some examples of automating updates to branches

• SO post
• Noxfile Recipes: Auto-Release
• I just thought this was interesting

Docs on GH Actions:

• Multiple jobs in a workflow
• Expressions
• Contexts
• Script Injection