Vitalii S. said: Mike W. sorry for my ignorance but I am working as developer. [...] Till that time you can take a break(I will read this topic and add all fixes posted and resolved here, also I will make detailed patch-note for you and other users). You can always contact me in Discord Mortimal#1488 for any questions you have (or proves of my work). I agree that doing solid patch-notes and similar are important for coordinating & communicating sheet changes What's your suggestion for the best method, given this environment, is it better to include that in the git commit messages, in the Pull Requests, add to the Readme, and/or mention things in this thread? For sheets I've done more work with, I've started to keep a Changelog in the GitHub folder for the sheet, to guaranteeing a reliable and simple overview of past changes. And even with putting effort into making solid commit messages or mentioning things in the Pull Request, it's not as easy to check git history and jump between old pull request descriptions, as it it to simply read a Changlog.md that mentions what each release changed. Sure, for some smaller sheets it might be overkill, but I'm pretty sure the GURPS sheet would benefit from keeping a Changelog, instead of only saving/displaying the latest change. If you have another viewpoint, I'm eager to hear your thoughts as a professional developer and learn.