carrylex@lemmy.world to Programmer Humor@programming.dev · 2 months agoGitHub Actions radicalized melemmy.worldimagemessage-square5linkfedilinkarrow-up12arrow-down10file-text
arrow-up12arrow-down1imageGitHub Actions radicalized melemmy.worldcarrylex@lemmy.world to Programmer Humor@programming.dev · 2 months agomessage-square5linkfedilinkfile-text
minus-squareqaz@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoThe real problem is merging before waiting for that one slow CI pipeline to complete
minus-squarenous@programming.devlinkfedilinkEnglisharrow-up2·2 months agoOne problem is GHs auto-merge when ready button. It will merge when there are still tests running unless they are required. It would be much better if the auto merges took into account all checks and not just required ones.
minus-squarePotatoesFall@discuss.tchncs.delinkfedilinkarrow-up2·2 months agogitlab has a feature where you can set it to auto-merge when and if the CI completes successfully
The real problem is merging before waiting for that one slow CI pipeline to complete
One problem is GHs auto-merge when ready button. It will merge when there are still tests running unless they are required. It would be much better if the auto merges took into account all checks and not just required ones.
gitlab has a feature where you can set it to auto-merge when and if the CI completes successfully