Remove secrets and emails from a Git patch

Replace possible secrets, email addresses, paths, authors and commit messages in a local patch or diff. Review the text before sharing. The edited excerpt may no longer apply as a patch.

Patch or diff file

UTF-8 .patch or .diff, up to 2 MiB and 30,000 lines. Files stay in this tab. Nothing is executed or sent to GitHub.

Replace before sharing

Lines with common secret patterns and private-key blocks Email addresses File headers and local home-directory paths Author and signer fields Commit subjects and messages before each diff

Other terms to replace, one per lineUp to 30 terms, 2 to 200 characters each. Matching ignores letter case.

Choose a patch or diff to begin.

The output is a review excerpt and may no longer apply as a patch. Pattern matching can miss credentials. Review every line, including changes you expected to keep, before sharing.

Help with this task

Check a Git patch before sharing it

Prepare a patch excerpt for review

A patch can include credentials in added or removed lines, email addresses, local paths and a commit message written for an internal audience. Choose the replacements you need, add project-specific terms and prepare an excerpt. The summary reports replacement counts without listing matched secret values.

Keep the working patch separate

The downloaded text is marked as a review excerpt. Replacing paths or code can change line lengths, hunk context and file identities, so it may no longer apply with Git. Your original file stays unchanged. Binary patch data is omitted from the excerpt.

Secret patterns are a limited check. Encoded, split, unfamiliar or short credentials may remain, and some ordinary code may be replaced. Inspect the whole excerpt before sharing. If a real credential has already been shared, revoke or rotate it with its provider. This tool does not contact the provider or verify credentials.