Closed Eh2406 closed 1 month ago
Personally, i don't think it adds value, but I'm not opposed to having it. We should change it though to run directly when you put the PR up instead of later as it used to.
Personally, i don't think it adds value, but I'm not opposed to having it.
Same
We should change it though to run directly when you put the PR up instead of later as it used to.
I found that very annoying because CI would basically always be ❌, especially annoying when the commits it was mad about where going to get squashed away.
I am very troubled that CI let things merge after finding ❌. Why did that happen and what else got through?
We have recently successfully merged PR's that failed "Commit messages follow project guidelines" CI.
We should either give up on this check. Or fix CI (do not let them merge) and reset the dev branch (do not have them in the history) and reemerged the PR's.