mergesand are numerically named (e.g
bodywhich contains a front matter and body sections. The front matter part is used to store merge request metadata while the body section contains the content describing the merge request.
featthat will add a new file named
kit mr createcommand is used to create the merge request. First, we may check out the base branch:
1is the merge request unique identifier. You can specify an alternative number by using the
--targetflag species the target branch that will be merged into the base branch
master. For us, the
featbranch is our target branch.
--targetHashflag specifies the hash we expect the base branch to change to after a successful merge. We used
~to indicate that we want the current hash of the
targetbranch but you can explicitly provide the full hash if you wish.
1for which the push operation intends to fulfil. It tells the network that the intent is to fulfil a merge the new changes of the base branch according to match the approved target of a merge request with
--reverseto reverse the order. You can also limit the number of issues returned with
readcommand to read the comments of a specific merge request. Supposing there is a merge request with ID =
2, it can be read like this:
--reverseto reverse the order. You can also limit the number of comments returned with
closecommand. The example command below will close a merge request with ID=