You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.org
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,23 +204,23 @@ $ ./priv/gp_latencies.sh
204
204
6) A Basho engineer or community maintainer will review your patch
205
205
and merge it into the main repository or send you feedback.
206
206
207
-
# 🔐 Detect Secrets Enforcement
207
+
* 🔐 Detect Secrets Enforcement
208
208
209
209
This repository uses [`detect-secrets`](https://github.com/IBM/detect-secrets-stream) to prevent committing sensitive information like API keys, tokens, and passwords.
210
210
211
-
## 🚀 How It Works
211
+
** 🚀 How It Works
212
212
213
213
Secrets are tracked using a `.secrets.baseline` file. This file contains a hash of detected secret patterns and is version-controlled.
214
214
215
215
On every pull request, GitHub Actions will:
216
216
- Scan the codebase using the committed baseline.
217
217
- Fail the build if new untracked secrets are found.
218
218
219
-
## 🛠 Update the Baseline
219
+
** 🛠 Update the Baseline
220
220
221
221
If your PR is failing due to newly detected secrets (false positives or intentional additions), follow the steps below to update the baseline:
222
222
223
-
### ✅ One-Command Update
223
+
*** ✅ One-Command Update
224
224
225
225
Use the provided `Makefile` to automatically install and run `detect-secrets`, then clean up:
0 commit comments