You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you so much @dandavison for making a tool that I continue to use on a daily basis!
Up front: The "blame" highlighting functionality works great as-is, this is just an enhancement request.
I've started using the Blame functionality #761, and often the age of the code (or its specific commit) is not as relevant as simply who WROTE the code -- i.e., who can help me understand it better and answer any questions I have.
For example, if we take some code from the Linux kernel and do...
There are a lot of commits for various bits of this code, but for the most part it's a single author. It would be nice, if {timestamp} and {commit} are not listed in the format options, that we just do a comparison against the author name. This has the added benefit of reducing the reuse / recycling of colors used to do the highlighting.
Let me know what you think!
The text was updated successfully, but these errors were encountered:
Much Love ❤️
Thank you so much @dandavison for making a tool that I continue to use on a daily basis!
Up front: The "blame" highlighting functionality works great as-is, this is just an enhancement request.
I've started using the Blame functionality #761, and often the age of the code (or its specific commit) is not as relevant as simply who WROTE the code -- i.e., who can help me understand it better and answer any questions I have.
For example, if we take some code from the Linux kernel and do...
There are a lot of commits for various bits of this code, but for the most part it's a single author. It would be nice, if
{timestamp}
and{commit}
are not listed in the format options, that we just do a comparison against the author name. This has the added benefit of reducing the reuse / recycling of colors used to do the highlighting.Let me know what you think!
The text was updated successfully, but these errors were encountered: