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

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}


[] :: cheeky way to abuse DMCA to avoid GitHub using your Git repos

[] using the mailing list model over the built-in issue model, and how this naturally federated and local first procedure is superior to github's standard issue approach

[]use git bisect while referencing maintainers of specific parts of code to narrow down to the code you should care about, then ask the maintainers about it - while putting in a minimum of effort.

[] using .gitignore the right way

Patch previous commits with rebases


If you need to change commit history:

  • Make another commit to make the change
  • Rebase starting at the commit you want to change
  • Squash the new commit with the old one in the history
  • Remove the second commit message (or merge it...)

This did change the commit time for my latest commit, which is something to watch out for.

How Git Works

[Neat writeup on the Git patience diff algorithm]

["Distributed, offline-first bug tracker embedded in git, with bridges"]

[Prototype Git GUI for Filmmaking]

["Pull github, bitbucket, and trac issues into taskwarrior"]

[Text-mode interface for git]

[bcongdon/git-trophy: ? Create a 3D Printed Model of Your Github Contributio]


  • A git repository can have multiple working trees - allowing you to check out more than one workspace at a time!

+ Among other things, this allows you to work on multiple branches at once without having multiple copies of the file, and maps git branches or tags to other directories on your system. Use it to check on different efforts on projects without messing up your current editing environment - to look at code from other branches locally and simultaneously, for example!

  •  :: Adds a new branch with a name associated with the final 
             component of PATH. `git worktree remove` and `git worktree prune` 
             both allow you to cut off external worktrees.
  • Flow example: latest develop, latest branch of work, and a third for reviewing pull requests and/or the work from other developers.


[track changes to a patch over time]

[git flow]: git extensions for high level repository operations

[explore git cli with natural language search]

[github is sinking]


[ A curated list of awesome Github Profile READMEs 📝]

[]i love the font choice and the gif here!

Code Review

[How to do a code review | eng-practices]


2022-11-02 23a47ba
2022-11-02 5087026
2022-10-27 d9a5da8
2021-09-22 52a677b
2021-09-21 7732812
2021-08-19 87d9551
2021-05-03 e8abf8e
2021-04-21 e031723
2021-01-20 35e386e
2021-01-18 af0b1e0
2021-01-17 675fddc
2021-01-15 d1b02d2
2021-01-15 4cf5fb9
2021-01-15 cccf2d4
2021-01-15 f2197ab
2021-01-15 5599273
2021-01-15 446991d
2021-01-12 cbfda85
2020-12-30 6b5e7b5
2020-11-15 a0eccac