Where is git-blame in SourceTree
57
I'd like to see who contributed which line/change to a file. git-blame does exactly that. So does SourceTree have a git-blame view?
git atlassian-sourcetree git-gui blame git-blame
edited Nov 11 '18 at 19:42
Ted
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
add a comment |
57
I'd like to see who contributed which line/change to a file. git-blame does exactly that. So does SourceTree have a git-blame view?
git atlassian-sourcetree git-gui blame git-blame
edited Nov 11 '18 at 19:42
Ted
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20
add a comment |
57
57
57
5
I'd like to see who contributed which line/change to a file. git-blame does exactly that. So does SourceTree have a git-blame view?
git atlassian-sourcetree git-gui blame git-blame
edited Nov 11 '18 at 19:42
Ted
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
I'd like to see who contributed which line/change to a file. git-blame does exactly that. So does SourceTree have a git-blame view?
git atlassian-sourcetree git-gui blame git-blame
git atlassian-sourcetree git-gui blame git-blame
edited Nov 11 '18 at 19:42
Ted
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
edited Nov 11 '18 at 19:42
Ted
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
edited Nov 11 '18 at 19:42
Ted
10.3k75465
edited Nov 11 '18 at 19:42
Ted
10.3k75465
edited Nov 11 '18 at 19:42
Ted
10.3k75465
10.3k75465
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
asked May 14 '12 at 10:45
artistoexartistoex
1,72931832
1,72931832
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20
add a comment |
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20
add a comment |
4 Answers
4
active
oldest
votes
73
Select a file, whether in the 'working copy' display or in the 'commit' display, and do one of three things:
- option-command-B
- menu bar :: Actions :: Blame Selected...
- contextual menu :: Blame Selected...
If the file you want to blame is not in the modified files list, you need to change the view to File Status View (View --> File Status View), then set the Sub menu to "Show All"
edited Mar 6 '14 at 20:24
chris
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
add a comment |
10
- Switch to the history view and select a commit that has the file you would like to blame.
- Right-click the file name and select Blame Selected.
Alternatively, you can right-click a file in the working tree or that has been staged and do the same thing.
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
add a comment |
2
Right click the file-> Blame selected.
You can find writer of Each line .
Trick: Make a minor change like adding a space in the file you want to find the file easily(File Status) in Source tree.
answered Jul 18 '17 at 15:35
AmitaAmita
4511
add a comment |
2
Sourcetree 3.0
Right click file > Annotate Selected
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f10581843%2fwhere-is-git-blame-in-sourcetree%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
73
Select a file, whether in the 'working copy' display or in the 'commit' display, and do one of three things:
- option-command-B
- menu bar :: Actions :: Blame Selected...
- contextual menu :: Blame Selected...
If the file you want to blame is not in the modified files list, you need to change the view to File Status View (View --> File Status View), then set the Sub menu to "Show All"
edited Mar 6 '14 at 20:24
chris
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
add a comment |
73
Select a file, whether in the 'working copy' display or in the 'commit' display, and do one of three things:
- option-command-B
- menu bar :: Actions :: Blame Selected...
- contextual menu :: Blame Selected...
If the file you want to blame is not in the modified files list, you need to change the view to File Status View (View --> File Status View), then set the Sub menu to "Show All"
edited Mar 6 '14 at 20:24
chris
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
add a comment |
73
73
73
Select a file, whether in the 'working copy' display or in the 'commit' display, and do one of three things:
- option-command-B
- menu bar :: Actions :: Blame Selected...
- contextual menu :: Blame Selected...
If the file you want to blame is not in the modified files list, you need to change the view to File Status View (View --> File Status View), then set the Sub menu to "Show All"
edited Mar 6 '14 at 20:24
chris
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
Select a file, whether in the 'working copy' display or in the 'commit' display, and do one of three things:
- option-command-B
- menu bar :: Actions :: Blame Selected...
- contextual menu :: Blame Selected...
If the file you want to blame is not in the modified files list, you need to change the view to File Status View (View --> File Status View), then set the Sub menu to "Show All"
edited Mar 6 '14 at 20:24
chris
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
edited Mar 6 '14 at 20:24
chris
1,65122131
edited Mar 6 '14 at 20:24
chris
1,65122131
edited Mar 6 '14 at 20:24
chris
1,65122131
1,65122131
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
answered May 14 '12 at 15:26
GoZonerGoZoner
47.6k1672122
47.6k1672122
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
add a comment |
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
4
4
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
Not sure what you are asking. A file changing since the last commit doesn't impact the blame (as the blame is based on the past commits). If the file hasn't change then in Source-Tree you'll find it by selecting 'Working Copy' and then 'Show All' (not 'Show Pending'). From there you can see all the files and select the one you want the blame for.
– GoZoner
May 21 '12 at 14:09
1
1
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
Ah yes, thanks! Haven't seen 'Show All' before.
– artistoex
May 21 '12 at 15:53
7
7
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
Note that for some inexplicable reason, this has changed from "Blame Selected" to "Annotate Selected"
– rinogo
Apr 10 '18 at 16:07
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
It seems like "Blame" and "Annotate" are near synonyms (for some spelunking on that, see this post on the git mailing list). I'm also suspecting some political correctness being injected.
– Erwin Wessels
May 24 '18 at 12:29
add a comment |
10
- Switch to the history view and select a commit that has the file you would like to blame.
- Right-click the file name and select Blame Selected.
Alternatively, you can right-click a file in the working tree or that has been staged and do the same thing.
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
add a comment |
10
- Switch to the history view and select a commit that has the file you would like to blame.
- Right-click the file name and select Blame Selected.
Alternatively, you can right-click a file in the working tree or that has been staged and do the same thing.
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
add a comment |
10
10
10
- Switch to the history view and select a commit that has the file you would like to blame.
- Right-click the file name and select Blame Selected.
Alternatively, you can right-click a file in the working tree or that has been staged and do the same thing.
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
- Switch to the history view and select a commit that has the file you would like to blame.
- Right-click the file name and select Blame Selected.
Alternatively, you can right-click a file in the working tree or that has been staged and do the same thing.
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
answered May 14 '12 at 10:48
Rohan SinghRohan Singh
12.4k13041
12.4k13041
add a comment |
add a comment |
2
Right click the file-> Blame selected.
You can find writer of Each line .
Trick: Make a minor change like adding a space in the file you want to find the file easily(File Status) in Source tree.
answered Jul 18 '17 at 15:35
AmitaAmita
4511
add a comment |
2
Right click the file-> Blame selected.
You can find writer of Each line .
Trick: Make a minor change like adding a space in the file you want to find the file easily(File Status) in Source tree.
answered Jul 18 '17 at 15:35
AmitaAmita
4511
add a comment |
2
2
2
Right click the file-> Blame selected.
You can find writer of Each line .
Trick: Make a minor change like adding a space in the file you want to find the file easily(File Status) in Source tree.
answered Jul 18 '17 at 15:35
AmitaAmita
4511
Right click the file-> Blame selected.
You can find writer of Each line .
Trick: Make a minor change like adding a space in the file you want to find the file easily(File Status) in Source tree.
answered Jul 18 '17 at 15:35
AmitaAmita
4511
answered Jul 18 '17 at 15:35
AmitaAmita
4511
answered Jul 18 '17 at 15:35
AmitaAmita
4511
answered Jul 18 '17 at 15:35
AmitaAmita
4511
4511
add a comment |
add a comment |
2
Sourcetree 3.0
Right click file > Annotate Selected
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
add a comment |
2
Sourcetree 3.0
Right click file > Annotate Selected
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
add a comment |
2
2
2
Sourcetree 3.0
Right click file > Annotate Selected
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
Sourcetree 3.0
Right click file > Annotate Selected
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
answered Nov 11 '18 at 17:58
TedTed
10.3k75465
10.3k75465
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
add a comment |
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Yup... why on earth they had to change the name...
– shadowsheep
Jan 28 at 8:20
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
Someone indeed opened an issue for that.
– shadowsheep
Jan 28 at 8:29
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f10581843%2fwhere-is-git-blame-in-sourcetree%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
These answers are just as I suspected - if you're trying to do a "blame" for an arbitrary file, it can be hard to find the file in the interface. One (far from perfect) shortcut I use is to just temporarily modify the file to cause it to appear as an "Unstaged file", at which point I can right-click it to access the blame.
– rinogo
Nov 14 '17 at 16:53
See Ted's answer (4th one). Sourcetree has cleaned up the language in version 3. We're not out to blame anyone, are we? We're just on a quest to understand. Not that we're getting much help. The windows that pops up with the result is not even searchable.
– Andy Weinstein
Jan 3 at 11:20