From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Automatic branch merging upon build completion Date: Fri, 06 Jul 2018 23:09:36 +0200 Message-ID: <87k1q89ilr.fsf_-_@gnu.org> References: <87r2ko6pby.fsf@elephly.net> <87r2ki2hso.fsf@gmail.com> <87fu0y11ir.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57267) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fbXz0-0004cu-UU for guix-devel@gnu.org; Fri, 06 Jul 2018 17:09:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fbXz0-0007h8-0n for guix-devel@gnu.org; Fri, 06 Jul 2018 17:09:38 -0400 In-Reply-To: <87fu0y11ir.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 05 Jul 2018 11:21:16 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org Hi Ricardo, Ricardo Wurmus skribis: > What do you think of pushing some package updates only to feature > branches that follow a certain naming convention (e.g. =E2=80=9C_update-f= oo=E2=80=9D for > updating the =E2=80=9Cfoo=E2=80=9D package), which causes Cuirass to buil= d them and > merge the branch into =E2=80=9Cmaster=E2=80=9D (semi-)automatically when = the build is > successful? FWIW I=E2=80=99m all for it, at least for feature updates=E2=80=94security = updates should still go directly to master. That=E2=80=99s a bit of work, though. I wonder if we could reuse similar features available in GitLab-style tools. Ludo=E2=80=99.