leds@feddit.dk to Programmer Humor@programming.dev · 10 months agoDO NOT MERGEfeddit.dkimagemessage-square33fedilinkarrow-up1253arrow-down19file-text
arrow-up1244arrow-down1imageDO NOT MERGEfeddit.dkleds@feddit.dk to Programmer Humor@programming.dev · 10 months agomessage-square33fedilinkfile-text
minus-squareaMockTie@beehaw.orglinkfedilinkarrow-up22arrow-down1·10 months agoWhy did they submit this as a pull request in the first place? Just commit it to a WIP branch until it’s ready to merge. Am I missing something?
minus-squarebrisk@aussie.zonelinkfedilinkarrow-up30·10 months agoProbably to get some other benefitof the PR system, such as CI tests
minus-squareleds@feddit.dkOPlinkfedilinkarrow-up10·10 months agoDoes gerrit have a draft state? In azure devops you can mark PR as draft , won’t trigger any builds but you can still start them manually
minus-squarebeeng@discuss.tchncs.delinkfedilinkarrow-up4·10 months ago manually This is probably why the dev created a PR, less clicks
minus-squaresf1tzp@programming.devlinkfedilinkarrow-up2·10 months agoI don’t remember if it did when I used it. Our convention was to -2 your own change until it was ready to go 😅
minus-squareNotSteve_@lemmy.calinkfedilinkarrow-up7·10 months agoI do this often. It’s useful if you want to send it to your coworker for some early feedback or as others have said, have the CI run
minus-squareDr. JenkemAlinkfedilinkEnglisharrow-up5·edit-210 months agoIt’s been a while since I’ve worked with AOSP, but I had always understood it to be some weird shit with Google’s internal processes. The “do not merge” commits are all over the AOSP, or at least they used to be.
Why did they submit this as a pull request in the first place? Just commit it to a WIP branch until it’s ready to merge. Am I missing something?
Probably to get some other benefitof the PR system, such as CI tests
Does gerrit have a draft state? In azure devops you can mark PR as draft , won’t trigger any builds but you can still start them manually
This is probably why the dev created a PR, less clicks
I don’t remember if it did when I used it. Our convention was to -2 your own change until it was ready to go 😅
I do this often. It’s useful if you want to send it to your coworker for some early feedback or as others have said, have the CI run
It’s been a while since I’ve worked with AOSP, but I had always understood it to be some weird shit with Google’s internal processes. The “do not merge” commits are all over the AOSP, or at least they used to be.