Contributing
Thank you for giving your time to AppKernia. We value contributions that are verifiable, scoped, and easy for the next maintainer to continue.
Good first contributions include clearer documentation, equivalent zh-CN / en-US copy, missing unit or accessibility tests, complete platform evidence, and minimal issue reproductions.
- Fork Payhon/AppKernia.
- Create a branch from your fork.
- Read the root and relevant subproject
AGENTS.mdfiles. - Reproduce the problem in source mode.
- Make the smallest complete change without unrelated rewrites.
An API change updates Go route/application/repository, OpenAPI, migrations/sqlc when relevant, permission seeds, audit/security events, generated Admin/Mobile clients, and tests.
A pull request should explain why, what changed, API/database/permission/security impact, exact commands and exit codes, screenshot/device evidence for UI changes, unverified platforms, risks, and rollback.
If a platform cannot be run, say “not verified” or “blocked.” Never present a static check as physical-device acceptance.