merge - git multiple project merging -
we forking project own codebase, closely follow project forked from.
i see working this:
forked project develop initial changes rebrand product. wouldn't want share these changes original project, going forward want merge changes.
the way have setup separate repos have same history , add remotes each other.
the workflow thinking of this:
we should try work on feature branches , have 1 commit per feature can each git cherry-pick . whenever work on feature , make commit, git commit --amend in branch feature. when finalized can cherry-pick commit.
i don't because if feature gets changed after cherry picking developer needs remember not end create new commit.
i love way merge or rebase.
suggested workflow:
- new branch each feature
- developer commits feature branch
- when merging master branch do:
git merge --squash -m 'new feature' branchname
now, delete branch!
git branch -d branchname
- if developer needs fix or change feature, creates new branch master. else same.
the next merge appear different commit on master branch.
Comments
Post a Comment