Adds these are required checks for PRs (except on release branches where
they are still not required):
* shell-script-check
* markdown-lint-check
* misspell-check
This is still NOT a required check:
* markdown-link-check
Also in this PR:
* Avoids running `markdown-link-check` at all on release branches since
it's generally expected to be red due to pinning the release download
link before tagging
I've been having a bit of trouble with the license check in our distro
repo, and I think it's helpful for it to be a separate github action
(also for visibility).
but do not make it a required check.
The reason for my change of mind here is:
When new library versions are released which break testLatestDeps, the
quick fix is to temporarily limit the upper bound, but it's not clear
what the quick fix is if we end up merging in a change which breaks
testLatestDeps (short of reverting the change, which then potentially
requires reengaging the contributor after they have moved on from the
PR).
Trask Stalnaker
Aaron Ai
Lauri Tulmin