all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Lendl <s.lendl@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [RFC v2 proxmox-backup] git-hooks: pre-commit runs cargo fmt --check
Date: Mon, 15 Jan 2024 10:28:26 +0100	[thread overview]
Message-ID: <87zfx7hrnp.fsf@gmail.com> (raw)
In-Reply-To: <e4cac481-c0ba-4092-9e2d-458e7aaac290@proxmox.com>

Thomas Lamprecht <t.lamprecht@proxmox.com> writes:

> Am 12/01/2024 um 15:43 schrieb Stefan Lendl:
>> * add a pre-commit hook that declines commiting if cargo fmt would make
>
> as said off-list I do not want anything that blocks committing,
> that is a PITA in development especially as this doesn't gains us
> much... so NAK!

It's easy to overwrite the checks when committing with `git commit --no-verify`

>
> Let's rather add a fmt --check test to the buildbot, then we get
> pinged on issues and a maintainer can just commit and push a cargo
> fmt run without that much fuzz.. 
>

I agree adding a fmt check to a CI make absolute sense. As of now the
buildbot is not triggered when sending a patch series. So the user will
not get feedback.
Guarding locally against not-formatted commits, prevents user from
sending these patches in the first place.
The intent was to ensure style compliance BEFORE sending a patch series
and not relying on a manual feedback process to identify this.

Once a CI is ready, this could and should be done in the CI.




  reply	other threads:[~2024-01-15  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 14:43 Stefan Lendl
2024-01-15  7:27 ` Thomas Lamprecht
2024-01-15  9:28   ` Stefan Lendl [this message]
2024-01-15  9:42     ` Thomas Lamprecht
2024-01-15 12:46       ` Lukas Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfx7hrnp.fsf@gmail.com \
    --to=s.lendl@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal