G'day, I head up the Sublime Merge team.
I'd love to hear your feedback on how we can improve the blame functionality! I can look into getting anything resolved there.
I'd love to hear your feedback on how we can improve the blame functionality! I can look into getting anything resolved there.
- One major improvement would be to provide a button to "View blame prior to this change" like Gitlab blame does (screenshot below):
https://drive.google.com/file/d/1BjXpQNlFgHKIJz-5SmJIxYB6fGD...
Because c++ codebases nowadays are full of commits that just reformat or refactors code (clang-format, update to smart pointers, update to new api, etc) and so if I just want to find out the original commit which introduced that codeline (because I want to know the _original_ motivation for it), it means in Gitlab I just need to click 3 or 4 times on said button to skip all such formats/refactor commits until I get to the one I'm interested in. That is easy in Gitlab, while SublimeMerge just let me click on the SHA of the last change for the codeline, and from there I'm lost I don't know how to keep "blaming back" like Gitlab easily let me.
- In the same vein of easy skipping blame changes until the one you want, it would help a lot supporting the git config setting blame.ignoreRevsFile:
https://git-scm.com/docs/git-config#Documentation/git-config...
Thanks and long life to Sublime!