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:

  1. fork repository "gitrepoa" , name "gitrepob".
  2. 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 
  1. create merge request @ gitlab.
  2. 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

Popular posts from this blog

elasticsearch - what is the equivalent data type for geo_point in hibernate search? -

Jenkins: find build number for git commit -

firebase - How to wait value in Ionic 2 -