docs: public-facing README + contributing notes; generic CI comments
This commit is contained in:
parent
41fdae8d06
commit
895bad9ac9
3 changed files with 17 additions and 17 deletions
|
|
@ -1,16 +1,9 @@
|
|||
# .forgejo/workflows/gitleaks.yml
|
||||
#
|
||||
# Sulkta canonical gitleaks workflow. Drop a copy into every public repo at
|
||||
# `.forgejo/workflows/gitleaks.yml` after the Forgejo act_runner is registered
|
||||
# (task #295).
|
||||
#
|
||||
# Pairs with the pre-receive hook installed on every bare repo — that one is
|
||||
# the strict enforcement layer (rejects the push); this one provides the
|
||||
# per-PR red ✗ that branch-protection rules can require before merge.
|
||||
#
|
||||
# Layer 1 (this workflow): visible per-PR status, can be a required check.
|
||||
# Layer 2 (pre-receive hook): strict enforcement at the server.
|
||||
# Layer 3 (the CI host cron sweep): nightly full-history sweep across all repos.
|
||||
# Scans the repository for committed secrets with gitleaks on every push and
|
||||
# pull request. Use it as a required status check via branch protection so a
|
||||
# leaking change cannot be merged. Works the same on GitHub Actions if you
|
||||
# move the file to `.github/workflows/`.
|
||||
|
||||
name: gitleaks
|
||||
|
||||
|
|
@ -38,4 +31,3 @@ jobs:
|
|||
- name: scan
|
||||
run: |
|
||||
./gitleaks detect --source . --no-banner --redact --verbose
|
||||
# re-run smoke 2026-05-28
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue