From c25bd51857c6ece05ab0fe390de8d6b1db51f797 Mon Sep 17 00:00:00 2001 From: Freso Date: Thu, 18 Sep 2025 12:02:07 +0000 Subject: [PATCH] =?UTF-8?q?fix(pre-commit):=20don=E2=80=99t=20default=20`v?= =?UTF-8?q?erbose`=20to=20on=20(#1015)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `verbose` was only set here as a work-around to make sure users saw the output of `validate` since there was no fail signal from the executable. As of https://code.forgejo.org/forgejo/runner/pulls/1009 there now is a signal that the validation failed which pre-commit can pick up on, so we no longer need to default `verbose` to be on. - bug fixes - [PR](https://code.forgejo.org/forgejo/runner/pulls/1015): fix(pre-commit): don’t default `verbose` to on Co-authored-by: Frederik “Freso” S. Olesen Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/1015 Reviewed-by: earl-warren Co-authored-by: Freso Co-committed-by: Freso --- .pre-commit-hooks.yaml | 3 --- 1 file changed, 3 deletions(-) diff --git a/.pre-commit-hooks.yaml b/.pre-commit-hooks.yaml index 0c195cb0..315c03e1 100644 --- a/.pre-commit-hooks.yaml +++ b/.pre-commit-hooks.yaml @@ -11,6 +11,3 @@ # Old names (without the pre- prefix) are deprecated since 4.0.0. minimum_pre_commit_version: '3.2.0' stages: [pre-commit, pre-merge-commit, pre-push, manual] - # validate doesn’t currently provide non-success exit codes, - # so falling back to always printing verbose output for now. - verbose: true