Overcommit
headwind
Our great sponsors
Overcommit | headwind | |
---|---|---|
5 | 9 | |
3,870 | 1,360 | |
- | - | |
6.8 | 0.0 | |
6 days ago | 9 months ago | |
Ruby | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Overcommit
-
Linting and Auto-formatting Ruby Code With RuboCop
A great way to ensure that all Ruby code in a project is linted and formatted properly before being checked into source control is by setting up a Git pre-commit hook that runs RuboCop on each staged file. This article will show you how to set it up with Overcommit, a tool for managing and configuring Git pre-commit hooks, but you can also integrate RuboCop with other tools if you already have an existing pre-commit workflow.
-
Tailwind CSS class sorter β the custom way
As a team we want to ensure that everybody commits our templates with classes rightly ordered. We use Overcommit to enforce consistency but any similar tool will do.
-
Run RuboCop on git commit with Overcommit Gem
# Use this file to configure the Overcommit hooks you wish to use. This will # extend the default configuration defined in: # https://github.com/sds/overcommit/blob/master/config/default.yml # # At the topmost level of this YAML file is a key representing type of hook # being run (e.g. pre-commit, commit-msg, etc.). Within each type you can # customize each hook, such as whether to only run it on certain files (via # `include`), whether to only display output if it fails (via `quiet`), etc. # # For a complete list of hooks, see: # https://github.com/sds/overcommit/tree/master/lib/overcommit/hook # # For a complete list of options that you can use to customize hooks, see: # https://github.com/sds/overcommit#configuration # # Uncomment the following lines to make the configuration take effect. PreCommit: RuboCop: enabled: true on_warn: fail # Treat all warnings as failures problem_on_unmodified_line: ignore # run RuboCop only on modified code
-
Automatically sorting your Tailwind CSS class names
Overcommit - run rustywind --write during git commit to update your files before you send them off to git
-
Migrating Tachyons to Tailwind CSS (III β learnings)
By the way, itβs nice that adding (or completely redefining) the scale system is so easy in Tailwind. On the other hand, care must be taken that modifying the defaults is not overused. In the end, we added an Overcommit rule banning further updates of the Tailwind configuration (of course, this can be temporarily disabled, when truly needed).
headwind
-
HyperUI Rewritten... What's Changed?
Added the tailwind-prettier-plugin as not everyone uses headwind
-
class order
Headwind is a nice addon for VS Code to sort classes automatically and warn you when using conflicting classes: https://github.com/heybourn/headwind
-
Cleaner CSS in your component templates with Tailwind and Headwind
The one I'm using is Headwind which defines itself as:
-
Tailwind CSS class sorter β the custom way
Headwind is a nice opinionated sorter which probably can be tweaked to understand our Slim templates but as a VS Code plugin it only works inside this particular IDE. We mostly use JetBrains RubyMine in our team and also needed a CLI version.
-
How to keep Tailwind DRY
If you are worried about property sort order (Tailwind is much more readable if you are) then you can use another tool to deal with that for you: Headwind. This VS Code extension will format your Tailwind classes on save and group them by their function, making sure everything is where you expect it.
-
Automatically sorting your Tailwind CSS class names
Headwind - a VS Code extension that sorts your CSS classes on save
-
Why Tailwind? A long term user perspective
I can suggest taking a look at Tailwind CSS Best Practice Patterns and Robin Malfait's Good Example to get an idea of how that would look like. For consistency, I can also recommend having a convention for class ordering or using headwind as an opinionated class sorter.
-
TailwindCSS JIT with Arbitrary Values
There's Headwind CSS, which orders classes predictably. But it doesn't move them to separate lines. This could be a config option if you're willing to write a pull request.
- How do you order class names in the markup?
What are some alternatives?
Rugged - ruby bindings to libgit2
Tailwind CSS - A utility-first CSS framework for rapid UI development.
git-up - NOT MAINTAINED
prettier-plugin-tailwindcss - A Prettier plugin for Tailwind CSS that automatically sorts classes based on our recommended class order.
git-whence - Find the merge and pull request a commit came from + fuzzy search for cherry-picks
tailblocks - Ready-to-use Tailwind CSS blocks.
git-auto-bisect - Find the first broken commit without having to learn git bisect
rustywind - CLI for organizing Tailwind CSS classes
git-spelunk - git-spelunk, an interactive git history tool
twin.macro - π¦ΉββοΈ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
docker-django-example - A production ready example Django app that's using Docker and Docker Compose.