I\'m working on a team with a few developers using git on BitBucket. We are all working on a dev
branch, not pushing to master
until a release.
I had the same problem. It happened that I have created .Readme file on the repository without pulling it first.
You may want to delete .Readme file or pull it before pushing.
The best option for me and it works and simple
git pull --rebase
then
git push
best of luck
you can use
git pull --rebase <your_reponame> <your_branch>
this will help incase you have some changes not yet registered on your local repo. especially README.md
This usually happens when the repo contains some items that are not there locally. So in order to push our changes, in this case we need to integrate the remote changes and then push.
So create a pull from remote
git pull origin master
Then push changes to that remote
git push origin master
Well actually github is much simpler than we think and absolutely it happens whenever we try to push even after we explicitly inserted some files in our git repository so, in order to fix the issue simply try..
: git pull
and then..
: git push
Note: if you accidently stuck in vim editor after pulling your repository than don't worry just close vim editor and try push :)
You need to input:
$ git pull
$ git fetch
$ git merge
If you use a git push origin master --force
, you will have a big problem.