I am currently testing out stash and I came across an issue where I download Sourcetree and set my credentials (Name and email) for the use of having a Author on commits. Every time I commit, it shows my author as 'unknown<mycomputername>'. I looked up this issue and it seems like one other person came across this, but was able to solve it by reentering their data under Tools-> Options. The only way I can fix this issue is by going to Repository -> Repository Settings -> Advanced and unclicking 'Use global user settings'. Can anyone explain to me the source for this issue? Is there a way to prevent this from occurring?
I'm no Sourcetree guru, but it seems like you did everything right initially.
You should be able to set your username and email globally for git through the command line though.
git config --global user.name "Jennifer Connor" git config --global user.email "email@example.com"
At least this way you'll be spared from needing to do this for each repo.
I have the same problem, but the accepted solution does not work for me. Neither does the workaround of the original poster.
Problem: When pushing unknown<mycomputername> is used.
remote: refs/heads/Feature-QCP-1055-plq-40k-80k-refactored: 96374b247370a007554fb59efbf4b85526c27bb0: expected committer email 'firstname.lastname@example.org' but found 'shortname@computername'[K remote: refs/heads/Feature-QCP-1055-plq-40k-80k-refactored: 96374b247370a007554fb59efbf4b85526c27bb0: expected committer name 'firstname lastname' but found 'unknown'[K
The author name and e-mail is configured in Tools -> Options -> General.
In Repository -> Repository Settings -> Advanced it does not matter if 'Use global user settings' is checked or not.
Using Sourcetree version 184.108.40.206 with embedded GIT 1.8.3.
I had a similar error after updating Sourcetree, and updating the git.config (global, local and system) to the correct user name and email didn't help. It turned out that the commit that I wanted to push had been made with the wrong name and email, so the remote wouldn't accept it. Running git commit --amend --reset-author fixed the problem once the correct information was in the config file (or in the Sourcetree options, which are equivalent).
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event