Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7Wyn-0002wS-MY for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jan 2022 06:19:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n7Wyl-0005Vw-Mr for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jan 2022 06:19:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7Wyl-0005VS-Dn for pgsql-hackers@lists.postgresql.org; Wed, 12 Jan 2022 06:19:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7Wyj-0006cq-3m for pgsql-hackers@lists.postgresql.org; Wed, 12 Jan 2022 06:19:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 20C6JMfg2949511; Wed, 12 Jan 2022 01:19:22 -0500 From: Tom Lane To: Thomas Munro cc: Julien Rouhaud , Bharath Rupireddy , Michael Paquier , Kyotaro Horiguchi , PostgreSQL Hackers Subject: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message) In-reply-to: References: <20211224.145134.1164706994861031206.horikyota.ntt@gmail.com> Comments: In-reply-to Julien Rouhaud message dated "Wed, 12 Jan 2022 14:09:21 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2949509.1641968362.1@sss.pgh.pa.us> Date: Wed, 12 Jan 2022 01:19:22 -0500 Message-ID: <2949510.1641968362@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Julien Rouhaud writes: > For this kind of situation I think that the usual solution is to use a > .txt extension to make sure that the cfbot won't try to apply it. Yeah ... this has come up before. Is there a documented way to attach files that the cfbot will ignore? Two specific scenarios seem to be interesting: 1. You are attaching patch(es) plus some non-patch files 2. You are attaching some random files, and would like to not displace the cfbot's idea of the latest patchset. I don't know exactly how to do either of those. regards, tom lane