3 ms·

What advantage does this have over git blame view?

• WorldMaker 11y ago
  Presumably the impetus is that if you fix a bunch of small things in a single commit it might be easier to compile the list of small things you changed by noting them as comments as you fix them rather than trying to remember them after the fact when it comes time to write a commit log for that commit. That said, philosophically I'd personally prefer to just commit the small features individually as a set of small commits, therefore you get a better git blame/praise experience with the end result, but I realize there is a wide spectrum of preferences on commit size and style.
  • Zezima 11y ago
    Yes, that was my intention when making this project. I prefer the practice of making very small changes and committing frequently with opulent use of branches. However, many of my peers and co-workers have a hard time following the small-commit workflow, so this project is really for them. Being able to mark small (but significant) changes in your code as you code definitely helps reduce some ambiguity in commit messages.
    • joncalhoun 11y ago
      Some feedback on that regard - if you could note line numbers or anything really w/ some of these it would probably help more than just messages. Eg "Concatenated strings in HelloWorld.js#12"
      • Zezima 11y ago
        Having the source & line number makes these much more useful. This is great feedback, thank you!
• volent 11y ago
  It's not the same thing at all. Git blame displays the last commits that updated your files lines. This gives you the ability to write your commit description while you code.
• Arnavion 11y ago
  git blame shows you commit messages for already-committed code. This builds the initial commit message when you want to commit the pending changes in the index.