Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Originaldate: Mon Mar 23, 2020 at 1:03 AM
Originalfrom: "V.Krishn" <vkrishn4@gmail.com>
Original: =?utf-8?q?On_3/23/20_12:21_AM,_Rasmus_Thomsen_wrote:
 =0D=0A>_Hello_list,?= =?utf-8?q?=0D=0A>_
 =0D=0A>_maxice8_(aka._Leo_on_our_Gitlab_instance)_and_I?=
 =?utf-8?q?_started_working_on=0D=0A>_mkmr,_a_small_python3_tool_to_create?=
 =?utf-8?q?_(and_manage)_merge_requests_on=0D=0A>_gitlab_instances_(from_t?=
 =?utf-8?q?he_CLI)._We_hope_that_this_tool_will_cut_back=0D=0A>_on_the_ove?=
 =?utf-8?q?rhead_Gitlab_introduces_(e.g._when_having_to_click_through=0D?=
 =?utf-8?q?=0A>_the_webUI)_and_maybe_this_will_even_help_people_migrate_fr?=
 =?utf-8?q?om_the_ML_to=0D=0A>_Gitlab_:)=0D=0A>_=0D=0A>_=0D=0A>_Setting_it?=
 =?utf-8?q?_up_is_pretty_easy:=0D=0A>_=0D=0A>_0._Create_a_Gitlab_account_a?=
 =?utf-8?q?nd_fork_=0D=0A>_https://gitlab.alpinelinux.org/alpine/aports=0D?=
 =?utf-8?q?=0A=0D=0ASounds_good,=0D=0A=0D=0AIf_I_have_a_repo_say,=0D=0Ahtt?=
 =?utf-8?q?ps://gitlab.alpinelinux.org/user1/aports=0D=0Acan_I_merge_branc?=
 =?utf-8?q?hes_'directly'_on_it_via_mkmr_scripts_=3F=0D=0Aeg._merge_user1/?=
 =?utf-8?q?aports/dev_to_user1/aports/master=0D=0A=0D=0A--_=0D=0ARegards,?=
 =?utf-8?q?=0D=0AV.Krishn=0D=0A?=
In-Reply-To: <2319c320-5796-3c00-9cbe-740942a20e34@gmail.com>
Date: Sun, 22 Mar 2020 16:50:35 -0300
Cc: "Rasmus Thomsen" <oss@cogitri.dev>
Subject: Re: Introducing mkmr
From: "maxice8" <thinkabit.ukim@gmail.com>
To: <vkrishn4@gmail.com>, <~alpine/devel@lists.alpinelinux.org>
Message-Id: <C1HMIGZOGAFA.2C3NW8H7JA5XD@enterprise>

On Mon Mar 23, 2020 at 1:03 AM, V.Krishn wrote:
> On 3/23/20 12:21 AM, Rasmus Thomsen wrote:
> > Hello list,
> >=20
> > maxice8 (aka. Leo on our Gitlab instance) and I started working on
> > mkmr, a small python3 tool to create (and manage) merge requests on
> > gitlab instances (from the CLI). We hope that this tool will cut back
> > on the overhead Gitlab introduces (e.g. when having to click through
> > the webUI) and maybe this will even help people migrate from the ML to
> > Gitlab :)
> >=20
> >=20
> > Setting it up is pretty easy:
> >=20
> > 0. Create a Gitlab account and fork=20
> > https://gitlab.alpinelinux.org/alpine/aports
>
>=20
> Sounds good,
>
>=20
> If I have a repo say,
> https://gitlab.alpinelinux.org/user1/aports
> can I merge branches 'directly' on it via mkmr scripts ?
> eg. merge user1/aports/dev to user1/aports/master
>

If you have a merge request with the source_branch=3Ddev and the target_bra=
nch=3Dmaster then you can
indeed use mgmr to merge it.

All of my testing happens on Alpine Linux's aports where i have my repo-for=
k as the --origin and
alpine/aports as my --target, but i don't see why it wouldn't work if both =
--origin and --target are
the same.

>=20
> --
> Regards,
> V.Krishn
>
>=20
>
>=20