I had forgotten that I moved from a local server to Bitbucket for my remote repository. I performed a commit using SourceTree with "push changes immediately to default" checked. The commit worked but the push failed.
I fixed the destination path to point to the proper Bitbucket repository. I clicked on push but got the message "no changes to push". When I check the repository on Bitbucket, I can see that the source files were not updated.
What gives? I'm stuck with changes on my local repository but I cannot push them to Bitbucket.
I am trying to push to
the error message I get says "repository is unrelated"
It looks like I may have caused the problem by copying the original files to a second folder, editing the files in that folder, moving the original files to a folder for obsolete files, then renaming the copy to the original name.
I have created a second repository to take up where the first one left off.
If someone knows a way to avoid this mess in the future, I would appreciate any tips.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs