pre-commit by Yelp
pre-commit
Python Poetry
EditorConfig
Git-Repo
Diff So Fancy
GitKraken
Gitential
Git-cliff
Changefeed
Changelog.gy
pre-commit
Git Flow
Changie
Diff So Fancy
Git-Repo
pre-commit by Yelp Git-cliffBased on our record, pre-commit by Yelp seems to be a lot more popular than Git-cliff. While we know about 142 links to pre-commit by Yelp, we've tracked only 3 mentions of Git-cliff. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
# See https://pre-commit.com for more information # See https://pre-commit.com/hooks.html for more hooks Repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v3.2.0 hooks: - id: trailing-whitespace - id: end-of-file-fixer - id: check-yaml - id: check-toml - id: check-added-large-files - repo: local hooks: - id: tox lint name: tox-validation ... - Source: dev.to / 5 months ago
Pre-commit hooks act as the first line of defense in maintaining code quality, seamlessly integrating with linters and code formatters. They automatically execute these tools each time a developer tries to commit code to the repository, ensuring the code adheres to the project's standards. If the hooks detect issues, the commit is paused until the issues are resolved, guaranteeing that only code meeting quality... - Source: dev.to / 5 months ago
Https://pre-commit.com/ can (and probably should) be used with any editor for such things. - Source: Hacker News / 5 months ago
Pre-commit Hooks: Pre-commit is a tool that can be set up to enforce coding rules and standards before you commit your changes to your code repository. This ensures that you can't even check in (commit) code that doesn't meet your standards. This allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks. - Source: dev.to / 7 months ago
Ah, fair enough! On my team we use pre-commit[0] a lot. I guess I would define the history to be something like "has this commit ever been run through our pre-commit hooks?". If you rewrite history, you'll (usually) produce commits that have not been through pre-commit (and they've therefore dodged a lot of static checks that might catch code that wasn't working, at that point in time). That gives some manner of... - Source: Hacker News / 7 months ago
Git-cliff is a terminal tool that can generate changelog from the Git history by using conventional commits, as well as by using regex-powered parsers and you can even change the changelog template itself by using a configuration file. This tool is a great example of text parsing on the terminal and also uses clap_mangen which generates man pages. Useful for anyone who is serious about looking into making a... - Source: dev.to / 5 months ago
Solutions exist for this. Our company does this with git-cliff. Using conventional commits, any commit labeled with the subject "www" will appear in our public changelog. Source: 12 months ago
This was primarily aimed to work with git-cliff to generate changelogs for GitHub releases, since tagging contributors would include them as contributors for the release, while also ensuring structured changelogs thanks to git-cliff. As of now, it requires a few extra steps to get it working with git-cliff, but the integration should be much better once the PR for post-processors is merged. Source: about 1 year ago
pre-commit - A slightly improved pre-commit hook for git
Changefeed - A beautiful changelog for your product in seconds
Python Poetry - Python packaging and dependency manager.
Changelog.gy - Every product needs a changelog
EditorConfig - EditorConfig is a file format and collection of text editor plugins for maintaining consistent coding styles between different editors and IDEs.
Git-Repo - Manage Gitlab, GitHub and Bitbucket from the command line