Add scheduled security scan workflow
This commit is contained in:
@@ -50,6 +50,7 @@ files/release-notes.md -> docs/release-notes.md
|
||||
files/blueprint.md -> blueprint.md
|
||||
files/blueprint.json -> blueprint.json
|
||||
files/build-gitea.yml -> .gitea/workflows/build.yml
|
||||
files/security-scan-gitea.yml -> .gitea/workflows/security-scan.yml
|
||||
```
|
||||
|
||||
Skip `build-gitea.yml` when the project has no CI target yet. Skip README blueprint files when the project should keep a very small manual README.
|
||||
@@ -156,6 +157,8 @@ upload artifacts
|
||||
|
||||
Only publish artifacts to a package registry when the artifact names and credentials are known.
|
||||
|
||||
For releasable projects, config tools, apps, or repositories that process user data, secrets, or deployment files, also add `.gitea/workflows/security-scan.yml`. Keep the scheduled workflow conservative and review false positives before silencing checks.
|
||||
|
||||
### 7. Finish
|
||||
|
||||
Before final response:
|
||||
|
||||
Reference in New Issue
Block a user