These had some minor overlap checking that the JS is up to date and
there isn't any benefit in having them separate as the jobs are run in
parallel anyway.

Co-authored-by: Chris Gavin <chris@chrisgavin.me>

We can only analyze PRs against those branches we are analyzing on push.

Fix a minor issue in the update-release-branch.py script that performs a
call to `sorted` but doesn't use the output. Since `sorted` does not
operate in place, the call is currently useless. As a result, the function
`get_pr_for_commit` does not currently work as exected. I.e. it is
expected to return the "first" (i.e. lowest PR number), but actually it
returns the first in the list provided by GitHub.

As this is an advanced usage it makes more sense to work to getting this included in the documentation instead.

Also add example from README into workflow to confirm it is accurate.

Co-authored-by: Max Schaefer <54907921+max-schaefer@users.noreply.github.com>

Support is recommending we redirect users to a new page for formal support requests.

…into robertbrignull/runner_workflow