"Kill off CI jobs" - already possible?

bagder / github-feedback

Ideas and features I'd like to see GitHub implement

https://bagder.github.io/github-feedback

Creative Commons Zero v1.0 Universal

12 stars 1 forks source link

"Kill off CI jobs" - already possible? #1

Open The-Compiler opened 3 years ago

The-Compiler commented 3 years ago

I think what you describe in Kill off CI jobs | github-feedback should already be possible: Canceling a workflow - GitHub Docs

Note however that "Write access to the repository is required to perform these steps.", so the PR author usually can't cancel the workflow themselves...

bagder commented 3 years ago

"workflow" sounds like that's specific for GitHub actions? We run CI jobs using 6 different services...

bagder commented 3 years ago

And yeah, I want the PR author to be able to do it. Like when realizing the PR is silly/wrong.

The-Compiler commented 3 years ago

Ah, yes - apologies, didn't realize with a lot of projects using GitHub Actions nowadays. That sounds like something those CI services would need to implement, though - as far as I know, there's no way for GitHub to talk back to those CI services, it's only the services reporting their status to GitHub.

bagder commented 3 years ago

Sure, something needs to be added. Code might need to be written. It's still not rocket science and it would make our lives a little better.