alpm-lint-check(1)

✨ alpm-lint-check(1) — General Commands Manual ✨

okay so bestie, buckle up 💖 this is alpm-lint-check from the General Commands Manual, section 1. she runs lints on your files and directories and honestly she's kind of the moment. no cap, this page is gonna be a whole vibe. 🦋

---

🌸 NAME 🌸

alpm-lint-check — run lints on a file or directory 💅

---

🎀 SYNOPSIS 🎀

alpm-lint check [-s|--scope] [-v|--verbose]... [-f|--format]
[-q|--quiet]... [-p|--pretty] [-l|--level] [-c|--config] [-o|--output]
[-h|--help] [DIR]

---

💜 DESCRIPTION 💜

Run lints on a file or directory. that's it, that's the whole thing, she's literally just here to lint. 🔥

By default, alpm-lint will try to determine the current linting scope based on the provided filename or on available files in the provided directory. so like, it's doing the vibe check for you — you don't gotta tell it what's up unless you want to. 👑

---

🫶 OPTIONS 🫶

• -s, --scope <SCOPE> — explicitly define the linting scope. bestie, using this option overrides the automatic detection, so you're the main character now 💅

Possible values:

• source-repository: lint rules with this scope are specific to an [alpm-source-repo]
• package: lint rules with this scope are specific to an [alpm-package]
• build-info: lint rules with this scope are specific to a single [BUILDINFO] file
• package-build: lint rules with this scope are specific to a single [PKGBUILD] file
• package-info: lint rules with this scope are specific to a single [PKGINFO] file
• source-info: lint rules with this scope are specific to a single [SRCINFO] file

• -v, --verbose — increase logging verbosity. the way that more -vs = more talking. she's yapping, and we love her for it 🗣️✨
• -f, --format <CHECK_FORMAT> [default: text] — the output format to use. if none is provided, any issues will be printed in human readable form 🧚

Possible values:

• text: human readable text
• json: the JSON output format

• -q, --quiet — decrease logging verbosity. shhh, she's being chill now 🙈
• -p, --pretty — pretty-print the output. slay, but heads up: has no effect if the output format can not be pretty printed 💀 (so like, don't expect magic where there's no magic)
• -l, --level <LEVEL> [default: warn] — the level of lints to consider. any lints with this level and above (more severe) will be shown. and ngl, if such lints are found, the command will return with an non-zero exit code. periodt. 🔥

Possible values:

• error: lint rules leading to errors
• deny: lint rules leading to denials
• warn: lint rules leading to warnings
• suggest: lint rules leading to suggestions

• -c, --config <LEVEL> — supply a lint config path. this overwrites any options from the project wide configuration file, so it's giving "I'm the captain now" 👑🫶
• -o, --output <FILE> — optional output file path. if not provided, output goes to stdout, which is the classic, iconic, never-miss default 🌈
• -h, --help — print help (see a summary with -h) ⭐
• [DIR] — an optional path to a file or directory to be linted 🌸

---

lowkey a warning but also just a reminder: -p/--pretty genuinely does nothing if the output format can't be pretty printed — that's not a bug, that's just how she is 💅

---

okay that's the whole page, bestie, go forth and lint responsibly 🎀

to close out: the footer of this manual page is just alpm-lint-check on the left and alpm-lint-check(1) on the right — no date, no version, nothing extra. so like, that's the entire sign-off. iconic minimalism fr fr 💖✨