<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>pre-commit</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/1556/feed"/>
    <updated>2026-04-25T09:11:58+00:00</updated>
    <id>https://links.biapy.com/guest/tags/1556/feed</id>
            <entry>
            <id>https://links.biapy.com/links/11711</id>
            <title type="text"><![CDATA[prek]]></title>
            <link rel="alternate" href="https://prek.j178.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11711"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[pre-commit is a framework to run hooks written in many languages, and it manages the language toolchain and dependencies for running the hooks.

prek is a reimagined version of pre-commit, built in Rust. It is designed to be a faster, dependency-free and drop-in alternative for it, while also providing some additional long-requested features.

- [prek @ GitHub](https://github.com/j178/prek).]]>
            </summary>
            <updated>2026-02-05T13:27:36+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2768</id>
            <title type="text"><![CDATA[Talisman]]></title>
            <link rel="alternate" href="https://thoughtworks.github.io/talisman/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2768"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Using a pre-commit hook, Talisman validates the outgoing changeset for things that look suspicious — such as tokens, passwords, and private keys. 

Talisman is a tool that scans git changesets to ensure that potential secrets or sensitive information do not leave the developer&amp;#039;s workstation.
It validates the outgoing changeset for things that look suspicious - such as potential SSH keys, authorization tokens, private keys etc.

- [Talisman @ GitHub](https://github.com/thoughtworks/talisman).]]>
            </summary>
            <updated>2025-08-28T23:37:33+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4926</id>
            <title type="text"><![CDATA[pre-commit]]></title>
            <link rel="alternate" href="https://pre-commit.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4926"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A framework for managing and maintaining multi-language pre-commit hooks. 

Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks.

- [pre-commit @ GitHub](https://github.com/pre-commit/pre-commit).

Related contents:

- [The Comprehensive Guide to pre-commit @ MangaD&amp;#039;s GitHub Gist](https://gist.github.com/MangaD/6a85ee73dd19c833270524269159ed6e).
- [pre-commit hooks are fundamentally broken @ the website of jyn](https://jyn.dev/pre-commit-hooks-are-fundamentally-broken).]]>
            </summary>
            <updated>2026-02-23T14:58:09+00:00</updated>
        </entry>
    </feed>
