Skip to content
Snippets Groups Projects
Commit 640689e4 authored by Benoit Ngo's avatar Benoit Ngo
Browse files

Update README.md

parent ef8ceb57
Branches master
No related tags found
No related merge requests found
......@@ -6,7 +6,7 @@ Have a look at [here](https://blog.algolia.com/master-git-rebase/)
Rebasing is about rewrite the GIT history. You can rewrite the GIT history from a specified commit, EG: `git rebase -i HEAD~3` will start rewriting the GIT history from the 3 last commit starting from the end.
Rebasing should **NEVER** be used on branch where multiple people are working (EG: common branches as developp and commit should **NOT** be rebased).
Rebasing should **NEVER** be used on branch where multiple people are working (EG: common branches as developp and master should **NOT** be rebased).
The main reason to not rebase a common branch is because there are branch created from theses common branch. **NEVER rebase a branch when a branch has been created from it** This is a warning, if you dont know what you are doing, please ask to a more experimented user.
Rebasing will rewrite the GIT history, that mean a `git push --force` will probably be used.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment