A short while ago I read in the comment section of an article here on HN regarding things to ask before joining a startup as a developer. The article itself was fairly interesting, but the comment section was booming about logging practices. So my questions are, from a Junior Developers stand, what is considered good logging? How often should I commit? What do I commit in regards to big changes, and what do I commit if there is only a typo correction? What and where are good ways to learn about this if my current job does not practice this?
Got a bit confused about terminology, I normally call putting a message in a log file "logging" but here you are referring to "source control" I believe.<p>I think it varies from company to company, some are more strict that others. Big changes you write a brief summary, leave a line and write a full on description. Small changes a small one line message is enough. Both can reference a ticket too. For pull requests, always squash your commits to one commit and make that as descriptive as possible (if required).