Re: updating merge request

2023-01-19 Thread Lukas-Fabian Moser
Am 20.01.23 um 07:38 schrieb Aaron Hill: On 2023-01-19 8:54 pm, David Zelinsky wrote: Am I misunderstanding something?  Or is what it says in 3.2 a mistake? If GitLab works similar to GitHub (which I have more experience with), any new commits to your branch should automatically be picked u

Re: updating merge request

2023-01-19 Thread Werner LEMBERG
>> Am I misunderstanding something? Or is what it says in 3.2 a >> mistake? > > If GitLab works similar to GitHub In this case, it does not, or rather, we don't want what is standard on GitHub. > any new commits to your branch should automatically be picked up as > part of the open merge/pull

Re: updating merge request

2023-01-19 Thread Aaron Hill
On 2023-01-19 8:54 pm, David Zelinsky wrote: Am I misunderstanding something? Or is what it says in 3.2 a mistake? If GitLab works similar to GitHub (which I have more experience with), any new commits to your branch should automatically be picked up as part of the open merge/pull request.

updating merge request

2023-01-19 Thread David Zelinsky
I made my first merge request the other day. I have made some changes in response to review comments, and I want to upload these. But I'm confused about instructions in the Contributor's Guide. My inclination is to commit the changes on my local branch and then push to the same dev/* branch in m