Connect Local to Bitbucket

—

### **1. Check Existing Repository**
First, ensure your local project is a Git repository. Run:

git status

If it's not a Git repository, initialize it:

git init

—

### **2. Add Bitbucket as a Remote**
Go to your Bitbucket repository in your browser and copy the repository URL.

Add the remote to your local project:

git remote add origin <repository-url>

For example:

git remote add origin git@bitbucket.org:username/repository-name.git

—

### **3. Pull the Bitbucket Branch**
To ensure your local project matches the branch structure on Bitbucket:

git pull origin <branch-name> --allow-unrelated-histories

Replace “ with the branch you want to connect to, e.g., `main` or `develop`.

—

### **4. Stage and Commit Local Changes**
Add your local files to Git and commit them:

git add .
git commit -m "Initial commit from local project"

—

### **5. Push to Bitbucket**
Push your changes to the Bitbucket branch:

git push -u origin <branch-name>

—

### **6. Verify Connection**
Check the status and remote configuration:

git remote -v

—

### Troubleshooting
– **Authentication Issues**: Ensure you have configured SSH keys or Personal Access Tokens for Bitbucket.
– For SSH: [Set up SSH for Bitbucket](https://support.atlassian.com/bitbucket-cloud/docs/set-up-an-ssh-key/)
– For HTTPS: Use a Bitbucket App Password.

– **Merge Conflicts**: If there are conflicts while pulling, resolve them, then commit and push again.

Let me know if you need help with any of these steps!

1. The `main` branch does not exist locally.
2. Your local branch is named differently (e.g., `master` or another name).

Here’s how to resolve it:

—

### **1. Check Your Current Branch**
Run the following command to check your current branch name:

git branch

If no branch is listed or you see `(no branch)`, you may not have a branch yet. If the branch name is `master`, that’s the one you’re working on.

—

### **2. Rename or Create the `main` Branch**
If your branch is named `master` but you need `main`, rename it:

git branch -m master main

If no branch exists, create a new `main` branch:

git checkout -b main

—

### **3. Link the `main` Branch to the Remote**
Set the upstream branch to Bitbucket:

git push -u origin main

—

### **4. Verify Remote and Branch**
Check the branches on the remote repository to ensure they exist and match:

git remote show origin

—

### **5. Common Issues**
– **Bitbucket Default Branch**: If Bitbucket is still using `master` as the default branch, update it in your repository settings on Bitbucket or push to `master` instead:

git push -u origin master

—

### **6. Start Fresh (If Needed)**
If there are no commits or branches, initialize your repository properly:

git checkout -b main
git add .
git commit -m "Initial commit"
git push -u origin main

Let me know if this helps or if you encounter further issues!

Please make sure you have the correct access rights
and the repository exists.

—

### **Steps to Fix the Issue**

#### **1. Remove the Old Host Key**
Remove the offending entry for `bitbucket.org` in your `~/.ssh/known_hosts` file. Use this command:

ssh-keygen -f "/home/admin1/.ssh/known_hosts" -R "bitbucket.org"

This removes the old cached key for `bitbucket.org`.

—

#### **2. Add the New Host Key**
Manually add the new SSH host key for `bitbucket.org`. Use this command to fetch the updated key:

ssh-keyscan bitbucket.org >> ~/.ssh/known_hosts

This will add the current host key for `bitbucket.org` to your known hosts.

—

#### **3. Verify the New Host Key**
You can verify the fingerprint of the new key against Bitbucket's documentation. As of now, the RSA fingerprint for `bitbucket.org` should be:

SHA256:46OSHA1Rmj8E8ERTC6xkNcmGOw9oFxYr0WF6zWW8l1E

If the fetched key matches, you're safe to proceed. Bitbucket provides details about their SSH host keys here: [Bitbucket SSH Host Key Documentation](https://bitbucket.org).

—

#### **4. Test Your SSH Connection**
To ensure your SSH setup works correctly, test the connection:

ssh -T git@bitbucket.org

You should see a response like:

authenticated via the following:
→ Public key ...
You can use git to connect to Bitbucket.

—

#### **5. Retry the Git Command**
Now, retry pushing to the repository:

git push -u origin main

—

### **Notes**
– This issue arises due to enhanced security measures (man-in-the-middle attack prevention).
– Always ensure you're adding trusted host keys to avoid compromising security.

Let me know if you encounter further issues!