So I'd created a new project instead of forking and it didn't give me an option to manually chose libfprint/libfprint as target for the merge request. Which is weird, I think github allows that at least... but I'm not sure and it's not important. I've re-created as fork and everything seems fine now.
On Sun, Jun 24, 2018 at 2:52 PM Bastien Nocera <had...@hadess.net> wrote: > On Sun, 2018-06-24 at 14:25 +0300, Igor Filatov wrote: > > Bastien, > > > > I've incorporated latest upstream changes so I could open a merge > > request but it looks like on gitlab I need a permission to do it. Or > > should I just send a patch? > > You don't have rights to commit directly to the libfprint repo (yet), > so the workflow would be: > - Click the "Fork" button at the top of the libfprint page: > https://gitlab.freedesktop.org/libfprint/libfprint > - This will create a fork in your personal space, under: > https://gitlab.freedesktop.org/users/<name>/projects > - Then push your work branch there > - Once you've pushed your branch, you should get a message in the "git > push" output telling you where to click to create a merge request, or > you can create one from the browse page for that branch, in the web UI. > > Don't forget to select the correct destination when creating the merge > request. It will eventually show up at: > https://gitlab.freedesktop.org/libfprint/libfprint/merge_requests > > Let me know if you run into any problems. > > The requests that were opened in the past were all create with branches > in the libfprint repository itself, so they're a little different, but > the workflow is similar. > > Cheers >
_______________________________________________ fprint mailing list fprint@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/fprint
