PRE-COMMIT-VALIDATE-MANIFEST(1)

πŸ“¦ version 4.7.0, in epel 10, fedora 43, fedora 44

✨ pre-commit-validate-manifest β€” bestie edition ✨

okay so this is a lil page from the pre-commit manual (User Commands section, if you're keeping track πŸ’…) and it's literally about checking that your .pre-commit-hooks.yaml files aren't a whole mess.


🌸 NAME 🌸

pre-commit-validate-manifest β€” validate .pre-commit-hooks.yaml files πŸŽ€

no cap, that's the whole job. it looks at your manifest and goes "mmm this is valid" or "bestie… no."


πŸ¦‹ SYNOPSIS πŸ¦‹

pre-commit validate-manifest [-h] [--color {auto,always,never}]
[filenames ...]

that's the shape of it. nothing scary. we love a compact synopsis. ✨


πŸ’– OPTIONS πŸ’–

🫢 POSITIONAL ARGUMENTS 🫢

  • filenames β€” the file(s) you want checked, bestie. drop them in and let the tool do its thing. πŸ“

πŸ’… OPTIONAL ARGUMENTS πŸ’…

  • -h, --help β€” shows you a help message and then exits. your classic "wait what does this do again" button. iconic, honestly. πŸ†˜
  • --color {auto,always,never} β€” decides whether the output gets that cute lil color treatment or stays plain. it takes one of exactly three values: auto, always, or never. and it defaults to auto, so if you don't say anything it'll figure it out itself. main character energy fr fr. 🌈
ngl the vibes here are: pass always if you want color no matter what, never if you want it gone, and auto if you trust the process. those are the only three options though β€” don't get creative, it's not that kind of party. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole pre-commit friend group, all linked up because they roll together:

and of course, the mothership herself:


that's the whole page, bestie. go validate those manifests. you got this. πŸ’œ

this lil slice of manual came from pre-commit, dated February 2025 β€” and the page itself is filed under the PRE-COMMIT-VALIDATE-MANIFEST(1) name, just so you always know where home is. πŸŽ€βœ¨

πŸ“¦ where this page comes from