git - GitHub Pull Requests Between Branches -


my organization making transition svn git (hosted on github) , have adopted git-flow branching model.

we have been using pull requests merge between branches. use github web interface process merge , close request.

pull requests merged --no-ff. merge commit occur in destination branch.

so.... merge develop master - happens after merge develop branch both behind (due merge commits not being in master) , ahead (due new work being done in develop).

over many iterations, end "develop branch both 23 commits behind , 7 commits ahead of master" - seems ridiculous. should not worry this? should merge manually , not through githuib web interface?

if reason develop ever behind because of merge commits, should able routinely schedule sync.

git fetch git checkout develop git merge --ff-only master git push 

if have hotfix branch went in, worst case above fail. you're going merge without --ff-only tag. that's perfectly acceptable , expected (see comment on answer).

while it's convenient use github's pull request system manage pulls other remotes, should internal cleanup , without using github.


Comments

Popular posts from this blog

java - WARN : org.springframework.web.servlet.PageNotFound - No mapping found for HTTP request with URI [/board/] in DispatcherServlet with name 'appServlet' -

html - Outlook 2010 Anchor (url/address/link) -

android - How to create dynamically Fragment pager adapter -