Can we suppress 'Run cancelled' notifications? #13015
Replies: 34 comments 15 replies
-
Thanks for the feedback @alec-maxoptra - there's not at the moment, I'm afraid. I think that there's an opportunity for us to improve our notifications, and we'll take your feedback into account when we look at that work. I'll make sure that this is on the backlog. Appreciate you taking the time. |
Beta Was this translation helpful? Give feedback.
-
This would be especially interesting for repositories using semantic-release where you definitely want to avoid multiple runs or a release workflow in parallel. |
Beta Was this translation helpful? Give feedback.
-
Just to add, I'm also getting frustrated by this. It's generating a lot of notification false positives which is teaching me to ignore notifications :-/ |
Beta Was this translation helpful? Give feedback.
-
In our team, stale runs are always canceled. This results in a massive number of notifications. I would be very happy if this could be changed. |
Beta Was this translation helpful? Give feedback.
-
same as ☝️, my inbox is constantly bombarded with these notifications. i have to manually select all and mark as done when that happens. it's cumbersome, and has led to me missing a notification among the noise at least a few times. |
Beta Was this translation helpful? Give feedback.
-
We have some checkers that re-run when developers push new commits to the branch of the pr. It doesn't make sense for in-progress workflows to continue, instead, we cancel them and re-run the checkers for the latest changes. Ideally, I expect it was possible to do something like: name: My workflow
on:
pull_request
concurrency:
group: ${{ github.workflow }}-PR${{ github.event.pull_request.number }}
cancel-in-progress: true
notify-if-canceled: false # this is not a real config please do not copy past it :) |
Beta Was this translation helpful? Give feedback.
-
the feature is still desired, but if you use gmail, just create a filter to archive/delete the email to avoid notifications. |
Beta Was this translation helpful? Give feedback.
-
Legitimate canceling by explicit concurrency section in the action should not generate email notifications, or at least should be configurable. Please fix it to motivate developers cancel unnecessary jobs and have more free Github runners for everyone. |
Beta Was this translation helpful? Give feedback.
-
Is this feature request under development? I see many developers with the same issue receiving bunch of cancelled workflow notifications in email.. pretty annoying! |
Beta Was this translation helpful? Give feedback.
-
our use case is we're using graphite (go check it out, it's awesome) to support stacked PRs. it uses rebase to keep branches in sync, which means every time i update the stack with code from the main branch, it force pushes each branch in the stack. for reasons i don't entirely understand, this always produces a lot of cancelled runs, i suppose it has to do with rebasing. the end result is that every time i sync, my github notifications inbox is spammed with countless messages and i have to manually select them all and mark as done. easy to miss real notifications this way. |
Beta Was this translation helpful? Give feedback.
-
I'd also love this, my CI is now set up to cancel runs on old commits when new commits are pushed, and this results in a lot of redundant emails. |
Beta Was this translation helpful? Give feedback.
-
This is driving me crazy. The work flow being cancelled is NORMAL. Multiple Devs check in before build is finished. It Cancels the build because some code changed. Why do we need an alert for this? This is not an error. |
Beta Was this translation helpful? Give feedback.
-
it's driving me crazy as well. is there another channel where we can report this, or should we accept that this will likely never get picked up? |
Beta Was this translation helpful? Give feedback.
-
Would also love a way to prevent emails for canceled work flows. |
Beta Was this translation helpful? Give feedback.
-
Canceled workflows should not send a failure email. It leads to a ton of false negatives, and ignoring possibly legitimate failure emails with github actions. |
Beta Was this translation helpful? Give feedback.
-
@thispaul me and at least almost 200 other people are frustrated by this for over 1.5 years now. i see you're a PM at github, could you update us on whether the team is aware of this issue? or point me to a person i can contact. to everyone who got an annoying notification because of this message: sorry. but i bet it's not as annoying as a constant stream of daily useless notifications from cancelled runs. in fact, i would urge anyone who reads this to reply in order to keep the discussion on the first page, and find and ping other members of github until this gets noticed. |
Beta Was this translation helpful? Give feedback.
-
Cancelled workflow ≠ Failed workflow please prioritize this issue thanks ^^ |
Beta Was this translation helpful? Give feedback.
-
I agree on this being annoying and not useful in lots of cases, so having a way to disable it would be nice |
Beta Was this translation helpful? Give feedback.
-
Please consider prioritizing a fix for this. |
Beta Was this translation helpful? Give feedback.
-
+1, getting spammed with "run cancelled" emails because I pushed a change while tests are running is rather annoying. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I just realized that the emails even fire when you MANUALLY cancel the workflow, not just if it was from a I do not need an email for an action I just manually undertook, it would be great if we could see some movement on this. It is really hard for me to notice any actual failures amongst all the cancelled ones. |
Beta Was this translation helpful? Give feedback.
-
We ended up removing a concurrency group in nixpkgs which runs on every PR due to notifications to contributors which I initially added to save wasted resources. |
Beta Was this translation helpful? Give feedback.
-
We would like to be able to suppress 'Run cancelled' notifications but still receive 'Run failed' notifications.
We have a 'cancel-in-progress: true' workflow triggered on push which builds a set of markdown files into HTML, and a team of copy-editors who push to this repository using a WYSIWYG editor.
This process results in many small commits to the repository, and so we get spammed by the 'Run cancelled' notifications.
Is there any way we can cancel a run without triggering a notification?
Beta Was this translation helpful? Give feedback.
All reactions