git-conventional-commits
detect-secrets
Our great sponsors
| git-conventional-commits | detect-secrets | |
|---|---|---|
| 3 | 1 | |
| 303 | 47 | |
| - | - | |
| 6.8 | 0.0 | |
| 28 days ago | about 2 years ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 only | Apache License 2.0 |
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.
detect-secrets
-
Exposed company credentials in first week of internship
(sh)It happens. Make sure they understand that you have learned from your mistake and plan to make a meaningful effort to prevent this from happening again. Be super proactive, propose a new way to mitigate future leaks of sensitive info: https://github.com/lirantal/detect-secrets
What are some alternatives?
Apollo-CustomApiCredentials - Tweak to use your own reddit API credentials in Apollo
simple-git-hooks - A simple git hooks manager for small projects
better-commits - A CLI for creating better commits following the conventional commits specification
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
desk - A lightweight workspace manager for the shell
husky - Git hooks made easy 🐶 woof!
not-autotools - A collection of awesome and self-documented m4 macros for GNU Autotools
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
git-scribe - ✍️ AI copilot for crafting insightful Git commit messages
talisman - Using a pre-commit hook, Talisman validates the outgoing changeset for things that look suspicious — such as tokens, passwords, and private keys.
editorconfig-vim - EditorConfig plugin for Vim
ESLint - Find and fix problems in your JavaScript code.