If I select a commit in my git-svn repo using the log view then the commit message is shown as (null) in the detail view containing the commit metadata info. This only happens in git-svn repos -- my regular git repos show the correct info.
This makes ST a lot less useful for me -- is there a place I can download the previous version until this is fixed?
EDIT: Ok, now I've downgraded to ST 1.3.1 but I *still* get (null) for the commit messages! This is the version I was using before and it used to work properly. I've checked 'git log' and the messages look fine there. I've tried removing and re-adding the bookmark for the repo.
Everything's fine here with 1.3.1.1 and 1.3.1, including git-svn repos. The only thing I can think of that would do that is commit text replacement settings, can you check Settings (top right of the repo window) > Advanced to see whether you have something set up there? I haven't seen that happen before though.
And yes to answer your question 1.2.9.1 is still available here if you need it until we get to the bottom of this: http://downloads.sourcetreeapp.com/SourceTree_1.2.9.1.dmg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, thanks! It looks like the upgrade process corrupted my custom commit text replacement. I had a complicated regex that turned a generic Jira project ref into a link (instead of requiring a new rule for each project prefix). After the upgrade it got turned into this:
Regex Pattern: \
Replace With:
Deleting that pattern fixed the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Had the same issue and edited my replacements yesterday. That fixed it. *But* the fixed replacement is broken again after a SourceTree restart. I removed the replacement, that "helps" :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You probably used a '#' character in the replacement text. This was a bug, it's been fixed in 1.3.2 which is available direct from the website now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.