3 ms·
Having the history of changes is a step, but the important part of that is the why those changes were made. Git can capture this with good commit messages. Do y
by eikenberry 2y ago
Having the history of changes is a step, but the important part of that is the why those changes were made. Git can capture this with good commit messages. Do you have any plans to capture that "why"?
- holoway 2y agoYep! The application of Change Sets is a similar moment to record the "why", alongside all the information about what was done. We have more to do here, along with adding things like RBAC that requires review before change sets can be applied based on ownership of resources, etc. But this is the plan!
- eikenberry 2y agoThanks for answering my questions! Look forward to playing with it.
- thayne 2y agoAnother nice thing about using code is you can easily include comments explaining why something is done a certain way, right next to the code that does it and thay is also included in the history.