Hi All, Working on a GIT model for my projects. 1. Three main repositories, bare public repo, maintainer repo, developer repo 2. Developer1 clones the public repo and makes feature1 branch, updates, commits changes and pulls/pushes. 3. Developer2 on their local repo does the same thing and pushes updates. 4. Maintainer get the green light to rebase feature1 branch with master - they pull the whole repo, rebase the feature1 branch with master and then push feature1. 5. Developer1 pulls feature1 brach again and continues to work, does a pull/push to feature1 on public repo. Now, main question is - given that in step 4 maintainer rebase the feature branch with master then pushed, he is committing a cardinal sin by rebasing a branch that has already been pushed to the public repo, so if anyone has made any changes based on the commits originally pushed that now have been rebased - developer who tries to push those changes will have issues. Will these be solved by executing of a pull? Sorry if these are trivial questions...still trying to wrap my head around GIT. Thank you for your help. Cheers, Julia -- View this message in context: http://git.661346.n2.nabble.com/Opinions-on-my-GIT-model-tp5941048p5941048.html Sent from the git mailing list archive at Nabble.com. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html