git-conventional-commits
editorconfig-vim
Our great sponsors
git-conventional-commits | editorconfig-vim | |
---|---|---|
3 | 134 | |
303 | 3,104 | |
- | 0.5% | |
6.8 | 4.5 | |
29 days ago | 15 days ago | |
JavaScript | Vim Script | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
git-conventional-commits
- Apollo dev posts backend code to Git to disprove Reddit’s claims of scrapping and inefficiency
-
Maintain consistent styles for developers working across various editors
> https://direnv.net/ -- when you cd to a directory, do things like set variables.
Just use dotenv instead.
https://asdf-vm.com/ -- manage and use specific versions of software. Can work with direnv too!
May be useful in some cases, but adds a global dependency on asdf itself.
> https://pre-commit.com/ -- git hooks that I personally found easier to manage than Husky.
Git hooks are disturbing and slow down and/or break advanced git interactions.
> https://github.com/qoomon/git-conventional-commits -- enforce standard commit messages. Works with pre-commit!
Only if you want to be so pedantic about them. I find it mostly a waste of time to enforce commit message style.
-
Automated Frontend Workflow
After installation, it will generate a lefthook.yml file which can be customized to perform a static code analysis before committing the code. For example, it can ensure that the git commit follows the git-conventional-commits, and use Prettier, ESLint, and Stylelint to check, format, and fix any file which will be committed and run any test related with Vitest depending on the filetype and run each in parallel.
editorconfig-vim
-
Most basic code formatting
These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file.
-
Taking the Language Server Protocol one step further
Hello,
Maybe you should check this project:
https://editorconfig.org/
Regards,
- How to config indentation per project?
-
How We Started Managing BSA Delivery Processes on GitHub
editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files.
-
Ask HN: What work/office purchase transformed your life?
Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`.
Each IDE is configured to:
- Not reformat code on its own
- Ignore whitespace
- Run `prettier` as a pre-commit hook
Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`).
Then in theory each developer can use whatever IDE they want, whatever whitespace settings they want (tabs vs spaces), and the end code committed to the repo is still the same.
-
Rider - Formatting across projects
I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css.
-
Is there any reason to keep the editorconfig plugin installed?
Does this mean I can completely get rid of this plugin?: https://github.com/editorconfig/editorconfig-vim
-
Is there really no support for editorconfig, yet?
[1] https://editorconfig.org
- How do you handle code formatting in a team?
-
Announcing C# Dev Kit for Visual Studio Code
I dunno who downvoted your question, but I believe you can use .editorconfig to set that up for you.
What are some alternatives?
Apollo-CustomApiCredentials - Tweak to use your own reddit API credentials in Apollo
nvim-projectconfig - neovim projectconfig
better-commits - A CLI for creating better commits following the conventional commits specification
pycodestyle - Simple Python style checker in one Python file
desk - A lightweight workspace manager for the shell
project-config.nvim - Per project config for Neovim
not-autotools - A collection of awesome and self-documented m4 macros for GNU Autotools
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
detect-secrets - A developer-friendly secrets detection tool for CI and pre-commit hooks based on Yelp's detect-secrets
prettier - Prettier is an opinionated code formatter.
git-scribe - ✍️ AI copilot for crafting insightful Git commit messages
emacs-solidity - The official solidity-mode for EMACS