Damien Caliste wrote:
> Ah, I see, when looking at the page of your project
> (https://git.merproject.org/deloptes/bluez5_buteo-syncfw), it is not
> defined as fork from mer-core. I guess, you created a new project and
> push there from your computer. For Gitlab to know it's a fork, you have
> to
Damien Caliste wrote:
> Strange, when you visit the branch page of your project
> (https://git.merproject.org/deloptes/bluez5_buteo-syncfw/branches) do
> you see "merge request" button for each branch ? Is it still returning
> error 403 when you click on one ?
>
> Ah, I see, when looking at the p
Hello,
Le 2019-07-30 11:00, deloptes a écrit :
OK, thank you again. I read the documentation [1] and [2] now and tried
it
accordingly, but when I click the New merge request from
bluez5_buteo-syncfw it goes to a new page "403" saying " You don't have
the
permission to access this page.
Strang
Chris Adams wrote:
> Usually you don't push to the main repository, but instead you create a
> private fork of the repository, push your changes there (e.g. to
> deloptes_bluez5 branch or something) and then create a merge request from
> your private fork to the upstream repository.
>
> Then the
