Sourcetree Windows 404 on Create Pull Request on the Web

[Steve Gale]

When committing any work to any repo I stage my changes, do not check "push changes immediately to origin/branch", select "Create Pull Request", type my comments, then click 'Commit'. Every time it 404's and pushes my commit to the remote. What gives?

Things I've done: refreshed OAuth token, deleted and re-cloned repos, restarted

[Steve Gale]

Any word on this?

[Mike Corsaro]

Could you try 3.0.9 and see if that fixes it? Thanks!

[Steve Gale]

Auth fail, even though my OAuth token was valid. I tried refreshing the token and trying again - same result.

[Mike Corsaro]

This is probably an issue with the git-credential-manager. Try downloading v1.18.3 here which should fix it.

[Steve Gale]

That fixed the new auth error. I'm still getting a 404 with automatic commit when I create a PR and do not check commit changes. Still two /'s after bitbucket.org in the URL.

[Mike Corsaro]

1. Open the repository
2. Click "Settings" in the main toolbar with the gear icon
3. Double-click/edit the "origin" item
4. Check the "URL / Path" and post that here
5. Optional: change the "Remote Account" to use the Bitbucket account you added previously.

[Steve Gale]

https://steveg-iotashome@bitbucket.org/iotashomedev/ec2-deployment.git

[Mike Corsaro]

Okay, so there's nothing wrong with the URL. Could you open the file "you repository/.git/sourcetreeconfig.json" and check the value "BaseUrl" under "RemoteProjectLinks" and ensure there isn't an '/' at the end?

[Steve Gale]

Yes, all of my repos have "BaseUrl": "https://bitbucket.org/" in their sourcetreeconfig.json files.

So I removed the / after .org, saved the file, opened sourcetree, made some changes to a file in the repo, staged changes, selected create PR, and it brought me to the PR creation page over HTTPS, but my changes were already committed to the repo (I did NOT check push changes to origin). So we're halfway there.

[Steve Gale]

Any more ideas or should I run away from this tire fire?

[Mike Corsaro]

Are you sure you didn't push to the repository? We haven't seen any other users seeing a push happen when a the PR link was opened. Did you check the commit log in Bitbucket to see when that commit was actually pushed?

[Steve Gale]

100% sure.

The PR link opened and allowed me to type in comments, but wouldn't let me commit because there were no changes - they were committed a few seconds earlier.

[Mike Corsaro]

Ah okay. Just a FYI:

[Steve Gale]

Yep, my client has the same message.

So maybe I'm missing something here. I just went through the same process of staging a file, writing a commit message, and creating a pull request through the GUI.

So what is the point of the "Push changes immediately" box if it is ignored and always pushed? Also, how am I supposed to make a pull request if there are no changes?
Or is this behavior due to the fact that I'm working on/updating master and not merging a remote branch INTO master?

[Mike Corsaro]

I see -- I thought you were using the context menu pull-request feature (right click on the branch in the sidebar).

The "Push changes immediately" box exists so you can push automatically after commiting (if you had "Create Pull Request" unchecked).

Working on master and merging into master won't do anything because they're the same branch.

[Steve Gale]

Okay Mike, I'm on the same page now - thank you for your help!

Is there an open bug report for this?

The app continuously rewrites the trailing slash to the "BaseUrl" string value "https://bitbucket.org/" inside the sourcetreeconfig.json file which forces me to check/edit the file before I want to create a PR in each of the repos I work in.

[Mike Corsaro]

Yeah -- the fix was back-ported and will be fixed in the next release (3.0.11) which should be released sometime tomorrow if everything works out 🙂

[Mike Corsaro]

Hello! Could you check which version you're on (Help > About)? There was a bug where we accidentally added an extra '\' at the end of 'bitbucket.org' when making a PR that was recently fixed. Thanks!

[Steve Gale]

I'm running version 3.0.8.2279