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

Can't push subtree

XMLWordPrintable

    • Severity 1 - Critical

      As requested in answer to my stackoverflow (http://stackoverflow.com/questions/24637748/cant-push-subtree-using-sourcetree) post I'm posting this potential bug here.

      Using a basic schema for git subtree I created 2 repository on Github: "project" and "framework" and made the followings:

      • Clone "project" repository
      • Add Subtree "framework" in a folder named "framework_dir"
      • Navigate through "project/framework_dir" and create test.txt
      • In the "project" working copy add test.txt to and commit it.

      Pushing "project" gives the right result on the project repo. I then try to push this change to "framework" but it loops endlessly without giving any errors.

      Same manipulation seems to work on the mac app on Mac OSX

      Thanks.

        1. 7ut37.png
          7ut37.png
          6 kB

            [SRCTREEWIN-1819] Can't push subtree

            Vipin Yadav added a comment -

            Hi,

            Please let us know if this is still happening on latest version 3.4.5.

            Thanks

            Vipin Yadav added a comment - Hi, Please let us know if this is still happening on latest version 3.4.5. Thanks

            Anphy Jose (Inactive) added a comment -

            ophilbert , teo_shaowei We are analyzing this issue, however couldn't reproduce in the latest version. Is the main repo and the sub repo having different authentication?

            Anphy Jose (Inactive) added a comment - ophilbert  , teo_shaowei We are analyzing this issue, however couldn't reproduce in the latest version. Is the main repo and the sub repo having different authentication?

            Alex Alex added a comment -

            Highly voting fot this feature. I put up with it for six months already and I don't want to wait more.

            Alex Alex added a comment - Highly voting fot this feature. I put up with it for six months already and I don't want to wait more.

            Ev Haus added a comment -

            This is now an issue for me after upgrading from 2.1 to 2.2.2. I didn't have the issue in 2.1

            Ev Haus added a comment - This is now an issue for me after upgrading from 2.1 to 2.2.2. I didn't have the issue in 2.1

            Andrew McAllister added a comment -

            When will this be fixed?!!! This issue has a level of "Critical", does that not mean anything at all?!!!

            Andrew McAllister added a comment - When will this be fixed?!!! This issue has a level of "Critical", does that not mean anything at all?!!!

            Andrew McAllister added a comment -

            I third it is an authentication issue.

            We are having the same issue with this, it appears that it is a password issue when you use HTTPS, we have switched to SSH and it works OK. The problem isn't limited to just PUSH it also doesn't work for PULL either. Can we have an update on this??

            Andrew McAllister added a comment - I third it is an authentication issue. We are having the same issue with this, it appears that it is a password issue when you use HTTPS, we have switched to SSH and it works OK. The problem isn't limited to just PUSH it also doesn't work for PULL either. Can we have an update on this??

            Robert Stehwien added a comment -

            I had to switch to SSH as well in order to push subtree commits on windows. It would be nice if it worked on https

            Robert Stehwien added a comment - I had to switch to SSH as well in order to push subtree commits on windows. It would be nice if it worked on https

            Teo_ShaoWei added a comment -

            Yes I would second that it is an authentication issue.

            I realized that my main repo connects to BitBucket via SSH, but sub repo connects to BitBucket via HTTP. That results in an infinite loop too (despite effectively on the same account).

            I changed my sub repo to connect via SSH, and the connection goes through.

            Teo_ShaoWei added a comment - Yes I would second that it is an authentication issue. I realized that my main repo connects to BitBucket via SSH, but sub repo connects to BitBucket via HTTP. That results in an infinite loop too (despite effectively on the same account). I changed my sub repo to connect via SSH, and the connection goes through.

            Teo_ShaoWei added a comment -

            Hi, I am also facing the same issue. Just to float the issue up yupz.

            Teo_ShaoWei added a comment - Hi, I am also facing the same issue. Just to float the issue up yupz.

            Jani Similä added a comment -

            Also having this issue, is there any extra information we can supply to help solve this?

            Jani Similä added a comment - Also having this issue, is there any extra information we can supply to help solve this?

              Unassigned Unassigned
              267f2052c6b4 Olivier Ohbibi
              Affected customers:
              25 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: