Many editors have built-in support for committing code. Built-in support allows you commit code without having to switch to another application. The downside is that different editors have different levels of support for the various conventions you can use in a commit message.
But for quick and dirty commits, built-in support is very useful. Covering how every editor supports Git commits is out of the scope of this book, but you can see this in action with Atom in Chapter 5. For other editors, refer to their specific documentation.
FOR MORE READING
A lot of great guidance is out there for writing good commits. For example, the Git documentation at https://git-scm.com/book/en/v2/Distributed-Git- Contributing-to-a-Project has a section on contributing to a project and includes some Commit Guidelines.
I’m also a fan of a blog post by Chris Beams entitled “How to Write a Git Commit Message,” which you can read at https://chris.beams.io/posts/git-commit/
Source: Guthals Sarah, Haack Phil (2019), GitHub for Dummies, Wiley.