Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-13439

Can't create a pull request

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Low
    • None
    • 3.4.2-beta, 3.4.2
    • Bitbucket
    • None
    • Minor

    Description

      I just installed SourceTree version 3.4.2 and find that I cannot create a pull request.

      In the previous version (not remembering which one I had installed) I could solve this with the recommendation indicated in https://community.atlassian.com/t5/Sourcetree-questions/Unable-to-Create-Pull-Request-Default-Browser-Empty/qaq-p/1213475.

      But this no longer works. To be able to do the pull request I must do a push and generate it directly on the web, this does work. But if I try it from SourceTree, a dialog tells me that "You don't have any remotes wich have extended integration settings configured, blablabla ...".

      When trying a push, it is very likely that I need to refresh my OAuth token, which for some reason is lost for this operation only.

      As much as I update my credentials, do a refresh of the OAuth token, nothing works.

      I can do fetch, pull, tag, commit but not a pull request

      I think it is important to mention that my account in bitbucket is through google, that is, I have not created a user. Under this condition, to reproduce the behavior you just have to create a branch from Sourcetree in any repository and then try to create a pull request.

      The Remote button on the toolbar never changes state, always showing the exclamation point even though my credentials and token are correct and up to date.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              66c10323202f LuisCarro
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: