KNEL/KNELProductionContainers
2
0
Fork 0
Code Pull Requests Actions Packages Releases Activity

docs(agents): clarify commit/push strategy; batch pushes; never push unvalidated builds

Browse Source
This commit is contained in:
Charles N Wyble - admin
2025-09-12 14:33:33 -05:00
parent abb7232ce0
commit 39a28bbf2f
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
AGENTS.md
View File

@@ -43,9 +43,17 @@ Package ~100 free/libre/open-source applications as Cloudron apps with a fast, c
- Optional: `cloudron install --image <app>:dev` tested from inside the packaging container using `cloudron` CLI, if available.
## Approval Gate and Push Policy
- After validation, present a summary of what changed and the validation output to the maintainer.
- Only on explicit approval run `git push origin main` for the package commit(s).
- Never force-push unless explicitly instructed.
- Commits: frequent, small, and descriptive commits are encouraged; no approval needed for local commits.
- After validation, present a concise summary of changes and validation output to the maintainer and request permission to push.
- Push only at “natural” points (coherent, validated milestones). Examples:
- First green build of a new package scaffold (image builds + container starts + health OK).
- A feature-complete slice (e.g., addon integration added and tested).
- A bug fix with verification.
- Pre-release stabilization checkpoint.
- Batch pushes to avoid noise (aim for 1–3 pushes per active app per work session).
- NEVER push a broken or non‑validated build.
- Only on explicit approval run `git push origin main` for package-affecting changes.
- Never force‑push unless explicitly instructed.
## Repository Hygiene
- Do not commit upstream repos. The directories `PackagingForCloudronWorkspace/Docker/` and `PackagingForCloudronWorkspace/NonDocker/` are gitignored on purpose.