Good shout! This is a great way for getting this behaviour without any CI changes at all.
The only downside to this is that it's hard to see what the actual issue is without going into the sea of red rspec logs. I prefer to have one CI job per specific thing that's being built/tested, but it's a bit more work to configure.
Configuring this in a chained workflow also means other jobs (like rspec, webpacker etc) can be prevented from even starting to execute, rather than each one being setup in parallel and all failing with the same error.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good shout! This is a great way for getting this behaviour without any CI changes at all.
The only downside to this is that it's hard to see what the actual issue is without going into the sea of red rspec logs. I prefer to have one CI job per specific thing that's being built/tested, but it's a bit more work to configure.
Configuring this in a chained workflow also means other jobs (like rspec, webpacker etc) can be prevented from even starting to execute, rather than each one being setup in parallel and all failing with the same error.