Comments
-
First, you'll need to create the repository (or repositories) on Bitbucket first. Leave them empty and do the rest from your system. Next, go to the local repo and add the remote: git remote add bitbucket https://username@bitbucket.org/owner/repo.git OR git remote add bitbucket git@bitbucket.org:owner/repo.git where…
-
Are you still having this problem?
-
Another sign that you're not connecting directly to Bitbucket: debug1: Remote protocol version 2.0, remote software version libssh-0.6.5
-
That is not the bitbucket.org server host key hash. I get the following: jredmond:~ jredmond$ ssh-keyscan -t dsa bitbucket.org | ssh-keygen -lf - # bitbucket.org:22 SSH-2.0-conker_1.1.11-210b09a app-126 1024 SHA256:RezPkAnH1sowiJM0NQXH90IohWdzHc3fAisEp7L3O3o bitbucket.org (DSA) jredmond:~ jredmond$ ssh-keyscan -t rsa…
-
https://test.bitbucket.io will only work if your Bitbucket username is "test". (That is not your username.) Use your own username in place of "test", in both the repository name and in the URL.
-
Is this for Bitbucket Cloud (bitbucket.org), or for Bitbucket Server? Is this a key for your user account, or for an automated system?
-
So there are two things going on here: 1. You've defined the local branch but not the way it corresponds to the version on origin. The suggested command should fix that. 2. You're working on master, but the version of master you have is not the same as the one on the repo you're trying to push to. You need to run git pull…
-
What else does it say? The server generally explains what the specific problem is.
-
This is typically an issue with either your local network's name server or with something at your ISP. Are you still seeing it?
-
The lock icon on the repo avatar or in the repo list indicates that the repository is private. Only users who've explicitly received access can get to the repo. You can make a repo public in the Settings, but that means that anybody can read or clone your code (even without authenticating, though you'll still be able to…
-
Were you prompted for a password? 401 is "Authentication required", so if you aren't providing credentials then you'll get that every time.
-
Should be fixed now. Sorry about that.
-
Which version of Chromium? Can you curl the page?
-
What are you trying to achieve with that? Are you trying to have all clones of the repo use the same set of remotes?
-
That git command only affects your local copy of the repo. What are you trying to do with the REST API?
-
It was not healthy at the time of your original question: https://status.bitbucket.org/incidents/2tc39v9wrqgd
-
No. Please read the linked blog post listed in the message.
-
You can make API calls to Bitbucket to create repositories; using a tool like curl, you can do that from the command line. For both Bitbucket Cloud and Bitbucket Server, it's a POST, but the parameters are a bit different for each: Bitbucket…
-
In Bitbucket Cloud (bitbucket.org), go to the Settings and select "Transfer repository" from the Repository Details page. The Settings are only available to users with administrative access to the repository.
-
That 403 isn't coming from Bitbucket - it's coming from Jenkins (or whatever server you're sending to that uses Jetty) - so you'll need to add credentials to the webhook.
-
That explains a lot, actually. Modern operating systems prioritize IPv6 traffic over IPv4 traffic, so if the IPv6 route is invalid or experiencing difficulty then the IPv4 connection will be delayed. You aren't experiencing this on Github because they still don't support IPv6. As a short-term measure, you can add this to…
-
Can you use any other protocol besides plain FTP? Is SCP an option for your host, or even SFTP?
-
The "Active" branch list shows open branches that have commits which are not on the main branch. The "Merged" list shows open branches that don't have anything that isn't on master. Neither list shows closed branches. Your branch is still open if it's in one of those lists. You can still push, pull, or do anything else…
-
Are you asking about Bitbucket Cloud or Bitbucket Server?
-
You'll need to add the files to git before committing them: git add hello-world This will tell git to start tracking the file named "hello-world". You can also list multiple files or use wildcards if that'd be faster. Once git knows to track "hello-world", then you can commit: git commit -am "put a useful commit message…
-
https://www.atlassian.com/legal/customer-agreement addresses all of this. You may be interested in Section 7, "Hosted Services Terms", and most specifically in Section 7.4, "Your Data": 7.4 Your Data. “Your Data” means any data, content, code, video, images or other materials of any type that you upload, submit or…
-
Why were you getting a redirect?
-
You can collect more information from SSH by adding `GIT_SSH_COMMAND="ssh -v"` before your command. (You can also get more verbose by using `-vv` or `-vvv` instead.) Just to clarify, though: when you say that you "have blocked port 22 for SSH on the server", are you referring to inbound connections to your server, or…
-
It's also worth remembering that most commits take place on someone's individual system, rather than on Bitbucket itself. Bitbucket (Cloud or Server) doesn't get any indication that a commit has happened until that commit is pushed.
-
Should be fixed now: https://status.bitbucket.org/incidents/f7bv30xmm8jx