• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      I have a bunch of projects using Git and everytime I push changes to the wiki repo, I am prompted for my user's password, and this is a hassle.

      It would be nice if a URI for cloning wiki repositories through SSH was provided, so that the account's SSH keys become usable.

            [BCLOUD-4036] Clone wiki repos with Git using SSH (BB-4283)

            I am also having issues pushing to a wiki that I was able to push to last week.

            Legacy Bitbucket Cloud User (Inactive) added a comment - I am also having issues pushing to a wiki that I was able to push to last week.

            Is this issue resolved? I'm having the same problem

            Legacy Bitbucket Cloud User (Inactive) added a comment - Is this issue resolved? I'm having the same problem

            Issue BCLOUD-4075 was marked as a duplicate of this issue.

            aMarcus (Inactive) added a comment - Issue BCLOUD-4075 was marked as a duplicate of this issue.

            aiiie added a comment -

            We recently rolled out a major change to our SSH infrastructure, and it looks like we introduced a regression with wiki repos. I've just deployed a change that should fix this.

            Thanks for the report!

            aiiie added a comment - We recently rolled out a major change to our SSH infrastructure, and it looks like we introduced a regression with wiki repos. I've just deployed a change that should fix this. Thanks for the report!

            Issue BCLOUD-4067 was marked as a duplicate of this issue.

            aMarcus (Inactive) added a comment - Issue BCLOUD-4067 was marked as a duplicate of this issue.

            legacy-bitbucket-user added a comment -

            I'm also seeing this problem. It worked well some days ago. Hoping resolving it as soon.
            Thanks.

            legacy-bitbucket-user added a comment - I'm also seeing this problem. It worked well some days ago. Hoping resolving it as soon. Thanks.

            nexussays added a comment -

            I'm also seeing "remote end hung up unexpectedly" when trying to push/pull/clone from my repository SSH URL with {{

            {/wiki}

            }} appended to it.

            nexussays added a comment - I'm also seeing "remote end hung up unexpectedly" when trying to push/pull/clone from my repository SSH URL with {{ {/wiki} }} appended to it.

            This does not work for me. I get "remote end hung up unexpectedly". I have no problem accessing my repos over SSH - it is just the wiki. I can push to the same wikis over https.

            hyperionconsult added a comment - This does not work for me. I get "remote end hung up unexpectedly". I have no problem accessing my repos over SSH - it is just the wiki. I can push to the same wikis over https.

            Genba added a comment -

            I tried different URI combinations with {{

            {git remote add}

            }} but none of them worked. This one does!

            Thanks!

            Genba added a comment - I tried different URI combinations with {{ {git remote add} }} but none of them worked. This one does! Thanks!

            Hi Genba,

            You can clone the wiki over ssh, its just that there is not a URL provided for it.

            It is the same ssh url as the repo your wiki is attached to but with /wiki at the end.

            I hope this helps, cheers,

            Dylan

            Dylan Etkin added a comment - Hi Genba, You can clone the wiki over ssh, its just that there is not a URL provided for it. It is the same ssh url as the repo your wiki is attached to but with /wiki at the end. I hope this helps, cheers, Dylan

              93e1e5ba154a aiiie
              8c78ed49547c Genba
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: