4 ms·
If main/master isn't your production branch then allowing auto merge makes a lot of sense. And if your changes have been QA'd in staging and/or they aren't tha
by staindk 3y ago
If main/master isn't your production branch then allowing auto merge makes a lot of sense.
And if your changes have been QA'd in staging and/or they aren't that hectic (and are backwards compatible) then I think auto merge into prod can be fine too.
- veidr 3y agoYeah; I was assuming main is the production branch. I basically do not think "auto merge into prod" is ever OK, but then again, I let GitHub Copilot write 40-60% of my doc comments, so...
- capableweb 3y ago> I basically do not think "auto merge into prod" is ever OK, but then again, I let GitHub Copilot write 40-60% of my doc comments, so... Funny how different people can be :) I'll always try to make the main branch so clean that it can be deployed at any moment, and production will always use the latest commit as soon as possible. Basically, I'm doing CI + CD, but I understand it's not for everyone.