Git is a popular version control system.


Writing a Git Commit Message

Article Reference

  • Concise and consistent length and form
  • Communicate clear context about a change to fellow developers. Ensure that other developers understand why a change was made.


  • Separate subject from body with a blank line if the body is to be used.
  • Limit subject line to 50 characters
  • Capitalize subject line
  • Do not end with period
  • Use imperative mood; I ‘do’ this. Rationale: If applied, the commit will change these aspects of the code. Git’s own built-in conventions use this form.
  • Wrap at 72 characters
  • Use the body to explain ‘what’ and ‘why’ as necessary


I use this; Microsoft is bad but the community is good
Minimal free software repository. I would use this if the developer weren’t an egotistical BDFL.
Open source git repository; self host it

Organization Thoughts

github organization:

  • one repo per course - as most courses require partner work

= repo for coding challenge practice problems

  • managing research notes: ??? i am thinking a single org file for all of this
  • - that is, an org file in each project for the research notes pertaining to that project,
  • - and anotherorg file for misc. research ?? i will have to see how my research is used


It’s a good idea to reformat commits to make them more readable.

git reset HEAD~${number of commits to go back}
October 15, 2020