Mike Corsaro Atlassian Team

Hello! This has been a tough one to debug on our end. To attempt to address the issue, we've made a change that will be rolled out in the 2.5 release. Hopefully this will solve it. Please follow this issue for progress.

No worries -- we all have to start somewhere 🙂

Nevermind, solved!

Hello! Could you double check and see if your Unity project folder is inside the repository folder? Also, make sure the file filter drop-down is set to "Pending"

Hello! You probably have a space before your URL for the repo. Can you double-check and make sure the URL you're using doesn't have any special null-spaced characters, and doesn't begin with a space, or have a space between 'https' and the rest of the URL?

Hello! This is probably an issue with line-endings. Could you try the described solution here: https://jira.atlassian.com/browse/SRCTREEWIN-4006?focusedCommentId=844034&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-844034

Did you set Sourcetree to use System Git after installing it? If that still doesn't work, could you try adding your username to the remote repo URL? * Open the repo * Click "Settings" * Double click on the origin entry * Modify the URL / Path to include your username so that it looks something like this:…

Yep, that's just a typo. Just to clarify, even after removing all the git entries in Windows Credential Manager does it still prompt for a password?

Hello! This problem is caused by the Mercurial Credential Manager failing to extract on startup. I suspect that an anti-virus may be interfering or something like that. Could you try and see if the file specified is accessible by you? Thanks!

Seems like you don't have a system-wide install of git on your machine. That's OK: you've got 2 options: * Install git for windows (and make sure the setting for adding git to PATH is checked)* If you install git for windows system-wide, make sure the "Use system git" button is toggled in Options -> Git * OR, run the…

If auth fails when trying to pull or push, then it's because git is not using the correct credentials (and seeing as you've changed your password, then it probably still using the old one). I suspect that there's still some credentials in the Windows Credential Manager that's being used. Can you try the following? * Remove…

Glad to hear. 2.4.8 is currently rolling out now but does not fix this specific issue. The next release (2.5.X) will address it, as well as include enterprise-specific features (it should be rolling out to the beta group within the next few weeks). If you'd like to know more about this bug, you can track it here

Hey Dave, I think this might be a known bug that you're seeing. Can you try viewing the log with "All Branches" showing, but change "Date Order" to "Ancestor Order" and see if that looks right?

Interesting. So that dialog that you're seeing is coming from the Git Credential Manager -- it means that some credentials that Git is trying to use is incorrect. Could you try the following? * Open the accounts screen * Click "edit" on the second account * Enter your password for that account If that doesn't work, you can…

Hello! Could you give me more details about the error you're seeing? A screenshot would be great. Thanks!

Hello! Could you give me more details? When Sourcetree keeps prompting for a password it's usually due to an account that has incorrect credentials. * Which accounts you've added to Sourcetree * Are you using SSH or HTTPS? If Sourcetree keeps prompting for a password, you can try removing the account (Options -> Accounts),…

Hello! Could you try following the steps listed in this answer: https://community.atlassian.com/t5/Sourcetree-questions/Re-Can-t-install-SourceTree-due-to-login-problems/qaq-p/648803/comment-id/17299#M17299 Thanks!

Just to get this all in one post: if you're seeing this on Windows, do the following: * First, find and open your .gitconfig, which should be in: "C:\Users\USERNAME\.gitconfig" * Then, add the following, and do not wrap the path in single or double quotes: * If you're using System Git:* [init] templatedir = C:/Program…

Hello! So there's a lot of layers here, but first let's answer your questions: 1. Sourcetree does run on a VM, but will run slower as it has to deal with running in a VM, and over RDP at the same time 2. It really depends on the repository. If it has a lot of history (the .git folder is > 1GB) then it will be naturally…

This change happened quite a long time ago -- around version 1.9 which was released in Dec of 2016

Hello! A force push is a potentially dangerous operation as it rewrites history, therefore the ability to do so is locked behind a setting in the Options menu:

Hello! Git should be able to automatically track renames without needing to do anything (remember: git tracks content, not files). When tracking changes to a file in Sourcetree (right clicking on a file and selecting 'Log selected...'), make sure you check the "Follow renamed files" checkbox which should give you the…

Hello! Just to keep this up-to-date for others: we've recently released 2.4.8 which should fix this issue (SRCTREE-8264) You can find the release notes here

So if I understand correctly, pushing works in Sourcetree but not via command line?

Hello! It sounds like the URL for the remote is configured for HTTPS rather than SSH. Could you check the URL of the repo for me? * Open the repo * Click "Settings" * Double-click on the first item in the "Remote repository paths" list * Check the URL / Path* SSH paths look like this: git@contoso.com:ORG/REPO.git * HTTPS…

Hello! This issue will be fixed in the 2.4.8 release which should be available in the next week or so.

Hello! When getting the BugSplat report dialog, do you have a reference/stack ID? Thanks!

Hello! Could you upload the problematic file? This issue may have been fixed in the next release (2.4.8) which is in beta now. Thanks!

edit: already answered above

Hello! Can you go to "Options -> Git" and make sure "Perform submodule actions recursively" is checked? That should run `submodule update --init` when pulling.