nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Was blame removed from source tree? Or where did it move to?

sean harris_rl6pil

EDIT: I unaccepted the accepted answer because while it's an answer, it's quite frankly unacceptable. It was renamed to "annotate" to be more "friendly" to sensitive developers. What a user un-friendly thing to do. Sure, just rename standard features... What Atlassian dev manager got so butt hurt to feel the need to change this??

I feel like I'm going crazy, I used to use blame all the time by right clicking a file and selecting blame but it's not there anymore. I'm using v2.7.1. Screen Shot 2018-04-02 at 8.38.23 AM.png

Accepted answers

All comments

bgannin

We've renamed "Blame" to be a more user friendly "Annotate". Nobody is necessarily at fault, you're just figuring out who authored a particular line 😄 You're looking for "Annotate Selected…" in that menu, below "Log Selected…". HTH.

Brian Ganninger
Senior Mac Developer, Sourcetree

Nick Andren

This was a pretty frustrating change. "Annotate" and "blame" aren't even synonyms. I didn't even realize that it was the same feature until I stumbled across this post looking for why it was removed.

unknown

I agree I just spent 30mins trying to figure out where "blame" feature went in the web ui!! At least its still there

Steven Albano

Yeah, having "Blame" removed has been like loosing a limb. I have periodically searched for it since it was renamed. Glad I finally went on a great hunt for it after another dev complained about it to me too.

It is blame in git, and it was blame in Bit Bucket since I started using it, so "Annotate" is not user friendly. I am not trying to annotate the code, I am trying to find who it is written by.

"Authorship", "Authors", "Attribution" or "Contributors" might have been discoverable, at least.

How was this tested?

Kendall Totten

Speaking of bad functionality, there's no way to move or even delete answers. If I choose edit and delete the text, it wont let me save. And there's no general delete link. Sigh.

jaytavares

I agree with others. 'Annotate' is not a very accurate label for the function of this button. 'Blame' worked well. Perhaps 'Author' could work as well...

Jorge

One more against annotate and in favour of blame.

Terrible decision. Lost 15 minutes searching for it.

Bob Hallissy

So will you rename "Push" because it isn't nice to be pushy, and "Commit" because people who are committed are obviously radical fundamentalists? (all tongue-in-cheek, you understand)

I agree that this is about git semantics, and the term is "blame".

kryzarel

Seems like someone opened an issue suggesting "Annotate" be renamed back to "Blame". Vote on it to get the Source Tree team to hopefully notice it and revert this baffling change.
https://jira.atlassian.com/browse/BSERV-10886

shadowsheep

They are not the same, it should be nice and geek to leave it as 'blame' [-;

From: https://www.git-scm.com/docs/git-annotate

The only difference between this command and git-blame[1] is that they use slightly different output formats, and this command exists only for backward compatibility to support existing scripts, and provide a more familiar command name for people coming from other SCM systems.

aaron_tekton

Agreed. It should be 'blame.' I just figured SourceTree didn't have this feature until I came upon this post.

mattneub

You left out "Conflict". We don't have conflicts. We have "Lack of consensus."

mattneub

And there's no way to downvote an answer.

dgp

what a terrible decision.

This is a UI wrapper around an existing tool. The existing tool is blame.

Denise Skidmore

Interesting, didn't even know annotate was a valid git-scm tool. But the GUI completely re-formats the output, so the output format differences are a moot point? And Blame is the more commonly used tool?