CODEWITHSUNDEEP
gitlabgitlab-omnibus
eric
eric

Reputation: 140

patchset for gitlab merge request

Previously I am using gerrt and now quite new to gitlab. One question is that does gitlab have the idea of "patch set" concept which is in gerrit?

The problem is that developer working on feature branch seems to need a new commit to update a merge request, which would leave many git commit in a single merge request. And final merge operation would merge all the commits from a feature branch to master branch, while many middle commits are actually not need to push(e.g.: address the patch review comments).

In gerrit one commit could be amended and updated by many patch-set, and final merge request only push one commit in the end.

Upvotes: 2

Views: 1891

Answers (1)

Zipfer
Zipfer

Reputation: 174

For gitlab as a github approach a little bit different. The flow is:

git checkout -b feature-your-feature-realization
git commit -m 'some changes'
git push origin feature-your-feature-realization:feature-your-feature-realization

if you need to change something:

git commit --amend

Then force push to feature branch:

git push origin feature-your-feature-realization:feature-your-feature-realization --force

In this case, you will update your pull request.

Upvotes: 2

Related Questions