Trunk is an all-in-one solution for scalably checking, testing, merging, and monitoring code. With Trunk, developers write more secure code and ship faster.
Trunk Code Quality stands on top of the shoulders of incredible open-source linters, like
@geteslint
.
We're proud to announce our ESLint sponsorship and that the ESLint source code is now linted with Trunk Code Quality 🎉
Read more:
I'm sure you've hit GitHub merge conflicts before, but have you heard of "logical merge conflicts"?
GitHub will happily merge code with logical merge conflicts and break your main branch.
🧵1/n
If you maintain an open-source project, Trunk Code Quality is free to use and we’d love to help you improve your and your maintainers’ linting experience with a PR.
Leave a comment below!
Trunk Code Quality stands on top of the shoulders of incredible open-source linters, like
@geteslint
.
We're proud to announce our ESLint sponsorship and that the ESLint source code is now linted with Trunk Code Quality 🎉
Read more:
👉 Trunk 1.22.5 is released
✨ Improvements
- Help text improvements.
- trunk fmt will now use configured verbs when presenting results to the user.
🔧 Fixes
- Fix a crash in the LSP server when giving diagnostics for empty files.
- Trunk no longer erroneously follows symlinks
We dogfood Trunk Code Quality with Vale in our docs repo to help catch inconsistent spelling and capitalization. Code Quality gives us inline annotations when reviewing PRs.
Learn how you can do the same:
We dogfood Trunk Code Quality with Vale in our docs repo to help catch inconsistent spelling and capitalization. Code Quality gives us inline annotations when reviewing PRs.
Learn how you can do the same:
Do you lint your code?
@geteslint
has just started using
@trunkio
and so have I for my latest Open Source project!
Why? My favourite features are:
- multiple linters in one place (js, ts, markdown, yaml etc)
- consistent reporting in one place
- hold the line so we can move
👉 Trunk 1.22.5 is released
✨ Improvements
- Help text improvements.
- trunk fmt will now use configured verbs when presenting results to the user.
🔧 Fixes
- Fix a crash in the LSP server when giving diagnostics for empty files.
- Trunk no longer erroneously follows symlinks
@geteslint
@trunkio
Very excited to announce this partnership.
@geteslint
is the gold standard in js/ts linting and incredibly proud that they've now adopted code quality to keep their own repo in top form.
If it's good enough for the goose it's good enough for the gander.
A perfect summary of our complicated relationship with
@geteslint
.
Trunk uses Trunk to lint Trunk source code with ESLint who uses Trunk to run ESLint to lint ESLint source code.
As someone who recently started writing
@nextjs
and have been using ESLint by default, I LOVE THIS!
The folks at
@trunkio
have been shipping good stuff 🚀
Started the day sitting down to write an Open API spec for fun. I didn't start this... Ended up exploring conventional commits and then spent the evening discovering new VS code extensions. I can imagine there will now be a blog tomorrow on...
Blog posts being like buses, I have quickly whipped up an introductory one on Trunks code quality product. I have now embedded this automated tool seamlessly into my git workflow and I am very happy that code linting has now been completely solved!