Skip to main content
Run these checks before opening a pull request or promoting a commit to staging.

​
Application checks

1

Check application health

Open /up on the local HMIS origin. A healthy application returns HTTP 200.
Use http://localhost:8080/up for Docker Desktop.
2

Check migrations and the scheduler

The schedule must include op-visits:close-expired at 00:01.
3

Run automated tests

Run the smallest affected test set first, followed by the full project suite when preparing a release.
4

Build frontend assets

5

Exercise authentication

Sign in, select a branch, open the dashboard, sign out, and confirm that a user without the required role cannot access the administration panel.

​
Docker service checks

All required containers must be running, the application health check must pass, and the logs must contain no repeating database, permission, queue, or scheduler errors.

​
Optional integration checks

Complete the acceptance cases in Testing and validation, including duplicate delivery, unknown barcode, ASTM, and HL7/MLLP handling.

​
Evidence to retain

  • Commit identifier
  • Test command and result
  • Migration status
  • Frontend build result
  • Sanitized integration evidence when relevant
  • Known warnings or deviations
The commit is ready for staging when automated checks pass, the health endpoint returns 200, authentication works, and all affected workflows have retained acceptance evidence.