* 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
* Activate publishing of draft releases...
... And fix the message sending (missing parameter).
* publish_draft_release.sh now checks latest...
... release on github rather than just a tag
Idea is much the same as we currently do on polkadot - When a new tag is pushed (that fits our pattern for tags, e.g. v1.2.3), find a list of labelled changes and generate a changelog based on that. Create a draft release on Github and post about it on Matrix.
s3krit