Hi @o-200, thank you for this contribution. Your #3551 issue addresses CI improvements we've very recently been discussing.

Along with this brakeman fix, triggering the Postgresql GH Action on pushes would also be very valuable. Would you like to include that CI improvement in this current PR? Or maybe you'd prefer it as a separate PR?

Done, but what about 'Tests - MySQL' action? I'd prefer enabling it if the project uses two databases, but now it's action was disabled.

Hi @o-200, thank you for this contribution. Your #3551 issue addresses CI improvements we've very recently been discussing.
Along with this brakeman fix, triggering the Postgresql GH Action on pushes would also be very valuable. Would you like to include that CI improvement in this current PR? Or maybe you'd prefer it as a separate PR?

Done, but what about 'Tests - MySQL' action? I'd prefer enabling it if the project uses two databases, but now it's action was disabled.

Good question. It sounds like we will remove the MySQL support in the near future. (Just added a bit more about in the issue you created: #3551)

Thank you again for your work here @o-200. I had mentioned that these CI improvements were recently discussed. These discussions are related to a newly proposed release flow.

Sorry to complicate things with your contribution here. You have done a perfect job following our contributors guide, but the guide will have to be updated to reflect the new release flow. (I have described some of the needed updates here: #3554)

@andreadavanzo what would you propose here? I have just published the branch next-release/v5.0.2. Should the branch o-200:fix-brakeman be re-based off of that branch and should this PR also set it as the target?

hey, @aaronskiba, i see that CI "Danger / danger (pull_request)" is crushing. It is a expected behavior?

hey, @aaronskiba, i see that CI "Danger / danger (pull_request)" is crushing. It is a expected behavior?

Yes, that is unfortuately a behaviour we've noticed with PRs from outside of the main repo. Sorry about that.

Hi @o-200, sorry for the huge delay with this one.

Given our newer release flow, rather than trying to merge PR, I went ahead and cherry-picked your changes and added them to our newest release. I hope that's alright.

Thank you very much for your contribution here, these are some very nice improvements.