17 lines
939 B
Markdown
17 lines
939 B
Markdown
# Completion and release workflow
|
|
|
|
For every completed change in this repository, unless the user explicitly asks to
|
|
keep it local or defer release:
|
|
|
|
1. Finish the change and run the appropriate tests and checks.
|
|
2. Review the diff, then commit the completed work and push it to `origin`.
|
|
3. Deploy the pushed commit to the existing Dokku app `stride`, following
|
|
[docs/DEPLOYMENT.md](docs/DEPLOYMENT.md). Back up PostgreSQL before schema changes.
|
|
4. Verify the deployed Git revision, successful migrations, web and worker health,
|
|
and the public HTTPS `/health` endpoint. Check the changed feature where feasible.
|
|
5. Report the commit and deployment result. If release is blocked, state the exact
|
|
blocker and what has already completed; do not claim deployment succeeded.
|
|
|
|
This is the user's standing authorization to commit, push and deploy completed
|
|
changes. Preserve unrelated work and never commit secrets or database backups.
|