Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122429 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 925C71ACEBF for ; Sun, 18 Feb 2024 15:11:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1708269100; bh=9veS0XVYtrJLu41K+vNW3kY+NrCQ2hSaBYVXoDWHJQc=; h=Date:To:From:Cc:Subject:In-Reply-To:References:From; b=OoK0uGRphDcNbx2ZvhOWGZfUC8pKduz8ISsuRWcCmBkgCgt57ZICak1d95t/KgVaF 9su+55NDirNKZjMF+yq0itaK+3zz71RdilKzPKdndRlECAV3TJrvK4xVrc/7BqBmHU uEtMf68QVj8XQhOHt/P9qsNVG6Dg7WA9iCvFJ9LkclsxxFi8ehrBpDI89+j8cD/Pyi 9I2eAOP5GcxM+0aLmnQtFz6/hXmUabmILypuqwY7VmXqjouohiXqzw61KK4dV0G113 vouvfuvJtld5nzu8HVtdAlShVwNTNFrMu1lXTUCugTyEYFcwAjodW/eWhxYHbfYyCR fV6YHmASe4WjQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 21D11180059 for ; Sun, 18 Feb 2024 15:11:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 18 Feb 2024 07:11:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail; t=1708269091; x=1708528291; bh=9veS0XVYtrJLu41K+vNW3kY+NrCQ2hSaBYVXoDWHJQc=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=rbSViZwfx0/8whPCK/mvM3cpnjBpwyXLIodI6V03kvmAK7urbYFB4RQunv6HEJlDs OoTwD5EH4YCpBzBCRDDFDMmSJZ9Z+LREahOqmxAlhjUAknOeArfMkskIVnQwpaL/O/ tWgbc7NF0t7JIVDsYXNC5yj26VmnjTkmd10O9ZUyYW71dFRUygUjfpBTsNVQhVVQfG Jj3H/XYX16P9QmvwV7KtPpJwAUlocWS6JArbIMt6rO9ZoUbQmgp6welAsfqDKucwqu IoTdZ1O1gWhUjmiKmpEDrhKQelO6Ycitk5Xk2/GBruSXfpppHeWEbWbgpSNA5oQs6j y0OZsTPUpEfSA== Date: Sun, 18 Feb 2024 15:11:27 +0000 To: Ilija Tovilo Cc: PHP Internals List Subject: Re: [PHP-DEV] automatic formatting checks for pull requests? Message-ID: In-Reply-To: References: Feedback-ID: 96993444:user:proton Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") On Saturday, 17 February 2024 at 22:18, Ilija Tovilo wrote: > Right. Consistent code style is nice, but what we have now is really > not that bad. There are a couple things I'd want if we enforce code > style: >=20 > * Fixing the style should be easy, running a single command without > first pushing to CI. > * It should be fast too, so that I can easily run it for every commit, > preferably even on-save in my editor. > * The new code style should be applied only to newly added sections or > changed code, not entire files. Otherwise, we'll have many changes in > large files, with endless merge conflicts when merging up from lower > branches. Surely the best way is to apply the formatting tool on all branches that ar= e supported (even in security support). Have them be merged upwards, and then add the revisions of the commits to a= .git-blame-ignore-revs file so that git blame doesn't care about them. This should resolve the issue of making future merges difficult. Best regards, Gina P. Banyard