pre-commit by Yelp VS Shields.io

# 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

Shields.io — Quality metadata badges for open source projects. - Source: dev.to / 3 months ago

Badges are a great visual, and there are all kinds of badges. You just have to go to https://shields.io/, copy the code of the desired badge, and add it to your repo. You can use a badge to demonstrate the project's license, for example:. - Source: dev.to / 4 months ago

I just read the above article by the official rust blog. I wanted to ask what is "feature" and "badge" refered to as in this blog? What does it mean? At some places "shields.io badge " is mentioned. Are "badge" and "feature" some rust terminologies? It will be helpful if someone explains me this blog post in fewer words. Source: 5 months ago

Avoid using an unordered list for this section, as it can become challenging to read. Instead, the key is to categorize and group your skills and certifications, making them more organized and easier to manage. The specific edits required for this section depend on the number of skills, certifications, and other factors. If you have an extensive list, consider utilizing small badges from shields.io where... - Source: dev.to / 7 months ago

I would highly recommend adding (a few!) badges to any repository that you plan on publishing. You can get some great badges from https://shields.io/ along with the info on how to actually generate them. If your repository is public, this should be easy enough. I would say to avoid spamming a ton and having your README looks like a technicolor dreamland. Just having things like package health, SourceRank and... - Source: dev.to / 7 months ago