-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
title: "Finding linters" | ||
date: 2024-12-08T23:40:26+01:00 | ||
tags: | ||
- dev | ||
- devops | ||
--- | ||
|
||
A no-brainer and effective way to increase code quality in an organization is by | ||
the means of incorporating linters into your CI/CD pipeline. | ||
|
||
But where can you find them? | ||
|
||
<!--more--> | ||
|
||
Some sources of inspiration include curated "super-mega-hyper" linter packages, | ||
such as: | ||
|
||
- https://megalinter.io | ||
- https://github.com/super-linter/super-linter | ||
|
||
I am not generally a fan of employing these collections directly because it's | ||
not possible to exert tight control over them, and there's no security or | ||
reproducibility guarantee of their pipeline. | ||
|
||
Instead, I cherry-pick interesting / useful linters from their packs, | ||
effectively using them as serendipity sources for linters. | ||
|
||
Bonus points whenever there's out-of-the-box integration with the pre-commit.com | ||
framework i.e. whenever there's a `.pre-commit-config.yaml` file present at the | ||
root of the git repo. |