Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] [pre-commit] Use yamllint
Date: Tue, 28 Jul 2026 09:36:45 +0200	[thread overview]
Message-ID: <05b9efb5-8571-4eb5-a98f-798b0beb8be7@suse.de> (raw)
In-Reply-To: <20260717142530.61727-1-tdevries@suse.de>

On 7/17/26 4:25 PM, Tom de Vries wrote:
> I came across a formatting inconsistency in .pre-commit-config.yaml and
> investigated if there were pre-commit tools that could help with that.
> 
> I found yamllint [1].
> 
> The first patch fixes yamllint errors.
> 
> The second patch adds a pre-commit hook to check .pre-commit-config.yaml using yamllint.
> 

I came across a Red Hat Blog post "Check your YAML for errors with 
yamllint"  ( https://www.redhat.com/en/blog/check-yaml-yamllint ).

I'll consider that a review.

I'm pushing this.

Thanks,
- Tom

> [1] https://github.com/adrienverge/yamllint
> 
> Tom de Vries (2):
>    [pre-commit] Fix yamllint errors in .pre-commit-config.yaml
>    [pre-commit] Add yamllint hook
> 
>   .pre-commit-config.yaml | 120 +++++++++++++++++++++-------------------
>   1 file changed, 64 insertions(+), 56 deletions(-)
> 
> 
> base-commit: 0cdde1399d2d453569fe91c55b34b4879f8a6501


      parent reply	other threads:[~2026-07-28  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 14:25 Tom de Vries
2026-07-17 14:25 ` [PATCH 1/2] [pre-commit] Fix yamllint errors in .pre-commit-config.yaml Tom de Vries
2026-07-17 14:25 ` [PATCH 2/2] [pre-commit] Add yamllint hook Tom de Vries
2026-07-28  7:36 ` Tom de Vries [this message]

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=05b9efb5-8571-4eb5-a98f-798b0beb8be7@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox