-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are many 140.X workflows intentionally not processing any Events? #44563
Comments
assign pdmv |
New categories assigned: pdmv @AdrianoDee,@sunilUIET,@miquork you have been requested to review this Pull request/Issue and eventually sign? Thanks |
cms-bot internal usage |
A new Issue was created by @makortel. @smuzaffar, @makortel, @Dr15Jones, @antoniovilela, @rappoccio, @sextonkennedy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
Hi Matti, I really doubt this was intentional at the time of their introduction. So:
|
I think keeping one such "no events" workflow would indeed be useful. |
In #44413 it was noticed that at least workflows 140.X where X is 004, 006, 007, 008, 009, 011, 021 do not process any Events. While this was great to uncover the problem investigated in #44413, a question remains if that was intentional, or if these workflows were intended to process Events?
The text was updated successfully, but these errors were encountered: