* CI: pin md link checker's version to the previous release
* CI: add a whitelist for allowed GH actions pins
* CI: try master tip [skip ci]
* CI: return to a previous markdown-link-check dependency version [skip ci]
* CI: substitute %20 for a literal space [skip ci]
* CI: substitute %20 for a literal space
* add polkadot-companion-labels.yml
* fix polkadot companion job name
* add opened event to polkadot-companion-labels.yml
* Dont label on timeouts
* increase timeouts
* increase timeouts again... to be sure
* Switch to s3krit/await-status-action
Turns out Sibz/await-status-action looks at /ref/statuses, which lists ALL statuses (i.e., if you send a pending and a failure for the same context, it will see both and assume the job is still pending.). I forked and point at /ref/status, which shows a combined summary of each status (i.e., only ever shows the most recent status of a single context).
* Create release-tagging github action
Uses an action that I forked, which I retain control of for now. Can probably move it to the paritytech repo at some point
* Remove 'prereleased' trigger
`published` action is triggered whether the release is a pre-release or not.
* Update release-tagging.yml
* Remove superfluous cmment
Martin Pugh