Hi All, I’ve been thinking about the difficulty I sometimes have following changes to the code and I’m thinking that there would be value to make a practice of creating PRs when committing changes.
This would give us: 1. A clear explanation of the reasoning behind the change. 2. A good place to discuss changes. 3. A list of changes for release notes. 4. Force us to be neater about where and how we commit changes. Committers would be able to self-merge although when practical, I’d think it would be nice to wait a few hours to a day before doing so in case there’s an issue we didn’t think of. Thoughts? Harbs
