Received: from mail-pg1-f194.google.com (mail-pg1-f194.google.com [209.85.215.194]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id AFC8B782B28 for <~alpine/devel@lists.alpinelinux.org>; Sun, 22 Mar 2020 20:07:48 +0000 (UTC) Received: by mail-pg1-f194.google.com with SMTP id t3so6065092pgn.1 for <~alpine/devel@lists.alpinelinux.org>; Sun, 22 Mar 2020 13:07:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=reply-to:subject:references:from:organization:cc:to:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VuDD+YuGJD7GGxik40tWGGfJx8puTDHQ9fspS1mKcH4=; b=iqNYie2dCq77LR1Z9lk/Gq7xECBEl7cGSEffEc28BUccpxyR/DyCUWKAzWKh17LGJr 5D2NrFwCMCqVrvS8aE7MUprGv16dQnXJp4cbcSjFO5JBqHqcYg7w+qOmjwEkJBGEp5fj sDsythIiMUU7woAf8qV1RoQX+eevePAReB6EePXdJ90f8R7qHcyQrLpWQB8PU88sB+tp pYKd4c66Xi4COTHIuHZU2LeuHMgZXmG7IShbQidk6xa8xHzDcPJtQi7YtdJvcLMtuR4Z VWBfRcO78bS6qUS271rvH6qEL1rrZLeeB4jvkvf232KxjKHeKPatVkaRywOUk3pryfvn IuBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:from:organization:cc :to:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=VuDD+YuGJD7GGxik40tWGGfJx8puTDHQ9fspS1mKcH4=; b=Ki0Q764Aoc99iWK/D4o6muWrx4PfAQchEb3iC1LfQNilS2W+5lgjbKhksHIBQMtCyU vLyNMpPjelxHMYfWHfh3xlJPAakxaMvWp2+7iwDCxYDrOgi6AoQYt3VpMVBgrpVuQPi4 mmpuukB8XNtSg+ssjKu8BPHawGdWXemdeNVQxRGdAa+wY44NVPfsa6kOid5+xzXMmJXM AvKFgNwJemKZhEqpeh7Oi07rpD6KcCqOKcig7wD6+lKTpSJ1T194ApOIe8Mxj/hj6T0P A4T15WLaeuTsWlsCYpk7Z0gESa0jSEgwdcdXqg2pqRXiKDpZ33Y8GnW+UE+7efVK9r+g fPuw== X-Gm-Message-State: ANhLgQ0A/TvMU2F7J+vngIHg0cX18ZBLPh586O23HWJoqDt8ATCo+BSm ZaTsQsVTHPaCfP69hPUxQm4= X-Google-Smtp-Source: ADFU+vvhzvzQ0jzWzj6HM1Ii1toF0EpcNOh6jckMqjLaZjkr/CaK7sRzC6YrCZhvLnyCZ+pMWsE0sQ== X-Received: by 2002:a63:3d48:: with SMTP id k69mr17887606pga.395.1584907666657; Sun, 22 Mar 2020 13:07:46 -0700 (PDT) Received: from [0.0.0.0] ([117.211.51.26]) by smtp.gmail.com with ESMTPSA id q71sm4833087pfc.92.2020.03.22.13.07.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 Mar 2020 13:07:46 -0700 (PDT) Reply-To: vkrishn4@gmail.com Subject: Re: Introducing mkmr References: <38c03a13520d52e1418666015866a8e72893b41c.camel@cogitri.dev> <2319c320-5796-3c00-9cbe-740942a20e34@gmail.com> From: "V.Krishn" Organization: Insteps.net Cc: Rasmus Thomsen To: ~alpine/devel@lists.alpinelinux.org Message-ID: Date: Mon, 23 Mar 2020 01:37:28 +0530 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 3/23/20 1:14 AM, Rasmus Thomsen wrote: > Hello, > > I'm not quite certain if I understand the question correctly, but if you set both the upstream and the origin remote to user1/aports it'll create a MR from whatever branch you're on right now to user1/aports/master. Was more of a general API feature/question, wherein allowing me to, merge user1/aports/dev -> user1/aports/master but creating NO MR. Currently for given repo user1/aports at gitlab for same I would do, ---------- git clone http://.../user1/aports cd aports && git branch dev && git checkout dev ".. make all changes .." git commit ... git checkout master git merge dev, git push origin master ---------- what I would like to do is use API, and git clone http://.../user1/aports cd aports && git branch dev && git checkout dev ".. make all changes .." git commit ... git push origin dev Then use API or a feature in mkmr, 1. merge dev->master, 2. then send a MR for master (changes) ---------- but then (1) above may not be something in scope of mkmr maybe I need to go through the API as what can be done :( > > Regards, > > Rasmus Thomsen > > On March 22, 2020 7:33:35 PM UTC, "V.Krishn" wrote: >> On 3/23/20 12:21 AM, Rasmus Thomsen wrote: >>> Hello list, >>> >>> 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 :) >>> >>> >>> Setting it up is pretty easy: >>> >>> 0. Create a Gitlab account and fork >>> https://gitlab.alpinelinux.org/alpine/aports >> >> Sounds good, >> >> 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 >> >> -- >> Regards, >> V.Krishn > -- Regards, V.Krishn