aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMitsuo Tokumori <mitsuo@tokumori.xyz>2026-07-07 05:46:06 +0900
committerMitsuo Tokumori <mitsuo@tokumori.xyz>2026-07-07 05:46:06 +0900
commitaf84eae99f6ebb9eaefab8e8063da9b5c5c368e5 (patch)
treeb97306098757969857f3ecdf1f52c6959ba631da /README
parentd7be1d021d83114ca3a57cbffec25998b8185d17 (diff)
Update READMEHEADmaster
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 6a93a77..c838f80 100644
--- a/README
+++ b/README
@@ -49,4 +49,4 @@ man env
Just like the Internet, anything sensitive that git tracks is a pain to remove.
To remove it, the git history has to be rewritten. If others had cloned the
repository they'll need to re-clone it. And at that point, the commited secrets
-are already compromised.
+are already compromised. See https://stackoverflow.com/questions/872565/remove-sensitive-files-and-their-commits-from-git-history