I’m thinking about using git commits more than just documenting changes, but as a journal for my work as it advances. Like a lab notebook in code.

In 2008, GitHub’s developers could have opted to use git format-patch instead of teaching the world to juggle branches. Or they might have chosen to generate pull requests using the git request-pull command that’s existed in Git since 2005 and is still used by the Linux kernel maintainers today2.

I’m getting into stacked branches these day, but I should look into git request-pull too.

Rewrite Git history with a single drag-and-drop. Undo anything with ⌘Z. All speed, no bumps.

I just started using Sonar which is a new GitHub/GitLab issue tracker client available as a TestFlight beta.

I found that the app has a URL scheme, so asked developers if it was implemented, and they were kind enough to give me a brief documentation, just enough to create a starter script for myself.

Sonar is a new native Mac app for viewing and editing GitHub/GitLab issues. It’s lightning fast and stores your tasks locally so viewing, searching, and editing is instant (even offline).

I was looking for something like this for a while now.

There are a lot of good Git workflow patterns here.

Ha fejlesztő vagy, akkor az alábbi oldalt tedd el a bookmarkjaid közé és kezdd el alkalmazni az itt tanácsolt dolgokat:

If you haven’t given much thought to what makes a great Git commit message, it may be the case that you haven’t spent much time using git log and related tools. There is a vicious cycle here: because the commit history is unstructured and inconsistent, one doesn’t spend much time using or taking care of it. And because it doesn’t get used or taken care of, it remains unstructured and inconsistent.

Madarat tolláról, fejlesztőt git history-járól.