Repository navigation
Post status as "check run" instead of status #265
Description
Activity
In order to post a check run we need a GitHub App for bedevere.
I plan to work on this during core sprint.
Is it worth converting Bedevere to an app or should we just finally move this all over to GitHub Actions?
Reacted by MariattaSure. I'm more familiar with building GitHub Apps but if it can be done as Actions, that's great too.
We can talk about it at the core dev sprint if you want, but basically GitHub Actions get a webhook event just like apps and then you get to specify what you want GitHub to execute in a runner on your behalf. Obviously reusable actions make it easy to pull together reusable parts, but executing a Python script is dead-simple as well.
Metadata
Metadata
Assignees
Labels
No labels
It would be great if bedevere can post the "issue number", "news" and "backport PR" statuses as Check Runs instead of status
The other CIs like travis CI, Azure pipelines are already running as Check Run instead of status.
This will help simplify miss-islington's automerge logic so it doesn't have to check in both "status" and "check runs".
When this gets implemented, please coordinate the change with miss-islington to ensure that miss-islington knows what to do with this change.