gitlab - Git workflow - how to sanely sync forks without rewritng history? -
i working in large company , use git track changes in code. current workflow like:
- fork repository "gitrepoa" , name "gitrepob".
- introduce changes.
'
git clone <gitrepob> git remote add upstream <gitrepoa> git checkout -b new-feature vim <text-file> git add <text-file> git commit -m "commit message" git push -u origin new-feature - create merge request @ gitlab.
- the commit introduced me isn't perfect, have improve it. in meantime, other developers modify codebase , fork has synchronized.
.
git checkout master git fetch upstream git pull --rebase upstream master now local master branch date, don't know how bring new-feature branch state too. performing pull rebase changes ids commits have pushed (they aren't merged yet), occur multiple times in end.
how should use git not pollute history of gitrepoa?
wiki
Comments
Post a Comment