All Projects → tombruijn → lintje

tombruijn / lintje

Licence: MIT license
Lintje is an opinionated linter for Git.

Programming Languages

rust
11053 projects
ruby
36898 projects - #4 most used programming language

Projects that are alternatives of or similar to lintje

flycheck-joker
Clojure syntax checker (via Joker) for flycheck
Stars: ✭ 55 (+120%)
Mutual labels:  linter
go-perfguard
CPU-guided performance analyzer for Go
Stars: ✭ 58 (+132%)
Mutual labels:  linter
JavaScript-Styleguide
📃 The NullDev JavaScript Styleguide
Stars: ✭ 23 (-8%)
Mutual labels:  linter
roku-libs
Compilation of utilities for Roku development
Stars: ✭ 47 (+88%)
Mutual labels:  utilities
ramllint
RAML Linter
Stars: ✭ 18 (-28%)
Mutual labels:  linter
flake8-mypy
A plugin for flake8 integrating Mypy.
Stars: ✭ 103 (+312%)
Mutual labels:  linter
lints
Lint all your JavaScript, CSS, HTML, Markdown and Dockerfiles with a single command
Stars: ✭ 14 (-44%)
Mutual labels:  linter
sugar
moved to https://git.matthewbutterick.com/mbutterick/sugar
Stars: ✭ 19 (-24%)
Mutual labels:  utilities
JimmysUnityUtilities
A bunch of code I like to have on hand while working in Unity
Stars: ✭ 93 (+272%)
Mutual labels:  utilities
lint-html-with-css
Lint HTML with CSS. A collection of CSS snippets from the hashtag #lintHTMLwithCSS on twitter. These CSS snippets intend to warn developers about common mistakes made in HTML.
Stars: ✭ 35 (+40%)
Mutual labels:  linter
SacredUtils
Configuration utility for Sacred & Sacred Underworld with Material Design. Abandoned 05/07/2020.
Stars: ✭ 27 (+8%)
Mutual labels:  utilities
rebellion
A collection of core libraries for Racket
Stars: ✭ 78 (+212%)
Mutual labels:  utilities
danger-eslint
A Danger plugin for linting javascript with eslint.
Stars: ✭ 13 (-48%)
Mutual labels:  linter
EditorConfig-Action
🔎A GitHub Action to check, enforce & fix EditorConfig style violations
Stars: ✭ 40 (+60%)
Mutual labels:  linter
tsafe
🔩 The missing TypeScript utils
Stars: ✭ 285 (+1040%)
Mutual labels:  utilities
gsc
Go Source Checker
Stars: ✭ 15 (-40%)
Mutual labels:  linter
looppointer
An analyzer that checks for pointers to enclosing loop variables.
Stars: ✭ 30 (+20%)
Mutual labels:  linter
check-wheel-contents
Check your wheels have the right contents
Stars: ✭ 131 (+424%)
Mutual labels:  linter
rorshach
A watchman for your directories. Rorshach allows you to listen to file system changes and run commands when these events occur.
Stars: ✭ 26 (+4%)
Mutual labels:  utilities
sonar-css-plugin
SonarQube CSS / SCSS / Less Analyzer
Stars: ✭ 46 (+84%)
Mutual labels:  linter

Lintje


Lintje is an opinionated linter for Git. It lints commit messages based on a preconfigured set of rules focussed on promoting communication between people. The idea is to write commits meant for other people reading them during reviews and debug sessions 2+ months from now.

  • No configuration. Don't spend time configuring your Git commit linter and instead adopt a preconfigured set of rules.
  • Portable. Lintje is a Rust project built for several Operating Systems and has no dependencies. Drop it into your project and it works.

Documentation

Visit Lintje.dev for more information about Lintje, and the Lintje documentation.

Example

Given the last commit in a project is this:

Fix bug

When running lintje to lint the last commit, the output will be:

$ lintje
Error[SubjectCliche]: The subject does not explain the change in much detail
  9a2ae29:1:1: Fix bug
    |
  1 | Fix bug
    | ^^^^^^^ Describe the change in more detail

Error[MessagePresence]: No message body was found
  9a2ae29:3:1: Fix bug
    |
  1 | Fix bug
  2 |
  3 |
    | ^ Add a message body with context about the change and why it was made

Error[BranchNameTicketNumber]: A ticket number was detected in the branch name
  Branch:1: fix-123
  |
  | fix-123
  | ^^^^^^^ Remove the ticket number from the branch name or expand the branch name with more details

1 commit and branch inspected, 3 errors detected

For more usage examples, see the [usage docs].

Getting help

Need help with Lintje? Found a bug or have a question?

Reach out to me through the issue tracker, discussions, on Twitter @tombruijn (DMs are open) or on any Slack team you can find me on.

Development

Setup

Make sure Rust is installed before continuing.

cargo build

Testing

cargo test

Building

Docker is required to build all the different target releases using cross.

To build all different targets, run the build script:

rake build

The build output can be found in the dist/ directory.

Releases

Before release all the supported targets will be build. See Building for more information about the build step.

To release all different targets, run the release script:

rake release

The release will be pushed to GitHub.

Finally update the Lintje Homebrew tap.

Code of Conduct

This project has a Code of Conduct and contributors are expected to adhere to it.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].