Rebasing can be a real headache. You have to resolve the merge conflicts and continue rebasing. For example you can use the merge tool (which differs depending on your settings)
git mergetool
Then add your changes and go on
git rebase --continue
Good luck
More Related Contents:
- Remove folder and its contents from git/GitHub’s history
- Remove commit for good
- Error when pushing amended commit to remote [duplicate]
- Is there a way to cache https credentials for pushing commits?
- How to do a GitHub pull request
- Is it possible to create a remote repo on GitHub from the CLI without opening browser?
- Configure Git clients, like GitHub for Windows, to not ask for authentication
- Git push results in “Authentication Failed”
- GitHub: How to make a fork of public repository private?
- ! [rejected] master -> master (fetch first)
- Github file size limit changed 6/18/13. Can’t push now
- Trying to understand `git diff` and `git mv` rename detection mechanism
- git rebase basics
- Git push doesnt do anything over HTTPS
- Heroku: How to push different local Git branches to Heroku/master
- How do I rename a repository on GitHub?
- Send a pull request on GitHub for only latest commit
- How do you fork your own repository on GitHub?
- Adding a collaborator to my free GitHub account?
- Which is the smarter git protocol, ssh or git(over ssh) or https protocol?
- How to clone all repos at once from GitHub?
- How to get default Git branch?
- Unable to Connect to GitHub.com For Cloning
- Error when push commits with Github: fatal: could not read Username
- Deleting remote master branch, refused due to being the current branch
- Transfer git repositories from GitLab to GitHub – can we, how to and pitfalls (if any)?
- Create empty branch on GitHub
- Pushing a large github repo fails with “unable to push to unqualified destination: master”
- Git clone repository error: RPC failed; result=56, HTTP code = 200
- npm install package from github repo subfolder