Add dependency release and compliance automations
This commit is contained in:
@@ -52,6 +52,9 @@ files/blueprint.json -> blueprint.json
|
||||
files/build-gitea.yml -> .gitea/workflows/build.yml
|
||||
files/security-scan-gitea.yml -> .gitea/workflows/security-scan.yml
|
||||
files/repo-cleanup-gitea.yml -> .gitea/workflows/repo-cleanup.yml
|
||||
files/dependency-check-gitea.yml -> .gitea/workflows/dependency-check.yml
|
||||
files/release-dry-run-gitea.yml -> .gitea/workflows/release-dry-run.yml
|
||||
files/template-compliance-gitea.yml -> .gitea/workflows/template-compliance.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.
|
||||
@@ -162,6 +165,12 @@ For releasable projects, config tools, apps, or repositories that process user d
|
||||
|
||||
For active repositories, also add `.gitea/workflows/repo-cleanup.yml`. It should report cleanup candidates only; it must not delete files, branches, packages, or releases automatically.
|
||||
|
||||
For projects with dependencies, add `.gitea/workflows/dependency-check.yml`. It should report dependency health only; it must not edit dependency manifests or lockfiles automatically.
|
||||
|
||||
For releasable projects, add `.gitea/workflows/release-dry-run.yml`. It should verify release readiness only; it must not create tags, releases, packages, or artifacts automatically.
|
||||
|
||||
For Codex-maintained projects, add `.gitea/workflows/template-compliance.yml`. It should verify agent context and template hygiene without overwriting project-specific conventions.
|
||||
|
||||
### 7. Finish
|
||||
|
||||
Before final response:
|
||||
|
||||
Reference in New Issue
Block a user