AWS CodeCommit VS pre-commit by Yelp

AWS CodeCommit: secure, highly scalable, managed source control service that hosts private Git repositories. - Source: dev.to / about 2 months ago

AWS CodeCommit is AWS's hosted GitHub in the cloud. It is integrated with IAM and you should understand how different levels of permissions that can be granted to users of the service. Know what the AWSCodeCommitPowerUser policy is for. You can receive notifications via SNS to invoke downstream actions in AWS CodeBuild, AWS CodePipeline or other competing services. - Source: dev.to / 3 months ago

CodeCommit - 5 active users,50GB storage, and 10000 requests per month. - Source: dev.to / 3 months ago

Build – Used for all CodeCommit repositories and CodePipelines that are deployed within the landing zone. - Source: dev.to / 4 months ago

PR-Agent offers extensive pull request functionalities across various git providers: GitHub, GitLab, or Bitbucket, CodeCommit, Azure DevOps, Gerrit. - Source: dev.to / 5 months ago

# 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 / 6 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