SOURCE CONTROL
Git Workflow
Use focused branches and commits that support review, deployment, and rollback.
Production stability and security notice
Development changes must preserve working functionality, Provider isolation, role-based access, HIPAA auditability, released Mobile compatibility, and integration stability. Never deploy AI-generated or unreviewed code directly to production.
Commit Discipline
| Topic | Standard |
|---|---|
| Focused change | One commit should represent one coherent change. |
| Clear message | State the module and purpose, not only 'update file'. |
| Separate projects | Commit API, Web, and Mobile separately when they deploy independently. |
| No generated noise | Avoid unrelated formatting or generated-file changes. |
| Reviewability | Keep diffs small enough to understand. |
| Rollback readiness | A commit should be reversible without undoing unrelated work. |
Recommended Flow
- Pull the current branch.
Confirm local code matches the intended baseline.
- Create or use the approved working branch.
Keep the change isolated.
- Run checks.
Type check, build, and perform targeted testing.
- Review the diff.
Confirm no secrets, hard-coded Provider data, or unrelated changes.
- Commit and push.
Use a descriptive message and preserve deployment separation.