Greg Pflaum

The REST API supports autolinks now: https://github.blog/changelog/2021-08-02-apis-for-autolinks/ The GitHub BlogAPIs for custom autolinks to external resourcesAPIs for Autolinks

@BalzGuenat Are you using a [history file](https://github.com/rtcTo/rtc2git/wiki/Getting-your-History-Files)? You are very likely to have conflicts if you don't use a history file.

It looks like detect-secrets is simply not on the path in your build environment. I don't know what build pipeline tools you are using. Did your build move from a...

@puranss Do you have it working with another version of Python? The title implies the problem is new with Python 11.

@dryoni Are you still using detect-secrets? If your [audit tool](https://github.com/Yelp/detect-secrets/issues/310#issuecomment-674376195) works with the latest detect-secrets, are you able to publish it?

Upgrading from detect-secrets 1.4 to 1.5 is causing problems for us because detect-secrets-hook 1.5 updates the baseline file even if no new secrets are found. It returns exit code 3...

Updated the description with an additional problem that can happen when using xargs and scanning very many files.

@bender-the-greatest Do your files contain Unicode (non-ASCII) characters? It might be the problem reported in #641. I'm seeing the same thing: A scan on Linux finds secrets. A scan on...

Here's a file which demonstrates the problem. A scan on Windows doesn't report a potential secret. Save as `utf-8 right curly double quote.js`: ```javascript ({ PASSWORD: "test", // U+201D RIGHT_CURLY_DOUBLE_QUOTE...

@Architrixs Assuming you are running on Linux, you can ignore the exit code by adding `|| true` to the command, like this: ```sh git diff --staged --name-only -z | xargs...