|
Having a locked down main branch with code reviews seems to be a pretty low bar. But if it's really all that contentious, you can coax them in by focusing on the "release process" instead of their commit workflow. So for example, introduce a branch called "production" and, well, nobody is using it right now so might as well add some branch protection rules. They can continue to use their existing workflow to write and push and share quickly on main. The first few times you make a release, you can do the pull request yourself to go from main to production with a nicely written summary of all of the changes since last release. Once they're used to seeing you do that, slowly have them start to do the same. This is really just semantics, making production the real main and main some development branch, but it might come across better as "here's some entirely new thing we can do to get release notes written down" as opposed to "here's how we're going to change something you're already doing."
|
#
¿
Jun 17, 2023 01:26
|
|
|
|
| # ¿ May 19, 2024 00:29 |
|