gitsshwiki
I'm not sure if everyone experiences this – when I edit a BitBucket wiki locally (through a git repository) I have to enter my BitBucket password for every pull and push.
Is there any way around this?
I have ssh correctly configured to use a key that is unlocked by gnome-keyring. Pushing to the code repository for my project in BitBucket works fine – I do not need to enter either by BitBucket or ssh key password.
A free and open-source tool is Keybase :
Git supports remote helpers. And we've made an open source one.
Keybase's remote helper performs all the crypto while letting git do its thing. This might sound impressive, but Keybase has not reimplemented git from scratch. We provide a remote helper, powered by the excellent go-git project, which we've begun contributing to.
We bring to the table: (1) crypto, (2) team + multi-device key management, (3) a safer concept of identity.
It is end-to-end encrypted. It's hosted, like, say, GitHub, but only you (and teammates) can decrypt any of it. To Keybase, all is but a garbled mess. To you, it's a regular checkout with no extra steps.
Even your repository names and branch names are encrypted, and thus unreadable by Keybase staff or infiltrators.
Teamwork is supported via Keybase Teams :
A Keybase team is a named group of people, with flexible membership. Let's say you work on a project called Treehouse. You could register treehouse on Keybase. This team name is universal; there can be only one Keybase team with a given name.
Teams get chats and channels. The chat looks a bit like Slack or Discord:
But Keybase teamwork is end-to-end encrypted, which means you don't have to worry about server hacks.
Best Answer
The problem is that, when you clone the wiki's repository, the clone is done through HTTPS, since the link provided by Bitbucket uses HTTPS to access the repository. What you need is a way to access using SSH as the protocol, instead of HTTPS.
It is actually possible to access the wiki's Git repository through SSH, although Bitbucket does not provide the link to do that.
Thanks to a ticket on Bitbucket's issue tracking system, I found that you can access the wiki repository through SSH by using the same URI of the project's repository, but with
/wikiappended.So, if your project's repository is under
git@bitbucket.org:UserName/project-name.git, the wiki repository can be accessed atgit@bitbucket.org:UserName/project-name.git/wiki, instead of using the HTTPS URI provided by Bitbucket.This way, you can clone your wiki by running the command
or, if you have already cloned the wiki repository using HTTPS, you can change the
originremote to use SSH by running the commandI have already tried this, and it works perfectly! You will not be prompted for your password anymore, since Git is now using SSH with your SSH key to log into the server.