---
alwaysApply: false
globs: ["**/*"]
description: "OneUptime practices for assembling a pull request: branch, commits, description. Use when preparing a contribution, not when merging or handing to review."
---

# OneUptime Contribution Practices

Derived from OneUptime's CONTRIBUTING.md (GitHub Flow, Apache-2.0). The file
is deliberately lean; these are the practices it actually mandates.

- Follow GitHub Flow: branch from master, keep changes reviewable, and land
  everything through a pull request - never commit directly to the default
  branch.
- Every code change that adds behavior must add tests for that behavior, and
  the full test suite must pass before the change is proposed.
- API changes must update the corresponding documentation in the same change,
  not as a follow-up.
- Run the project's canonical auto-fix/format command (here: `npm run fix`)
  before committing so style stays consistent; do not hand-format against
  the tooling.
- Bug reports and fix descriptions must include steps to reproduce, expected
  versus actual behavior, and minimal sample code where relevant.
- Respect the repository's modular layout (separate services, agents, Helm
  charts); keep changes scoped to the module they concern rather than
  cross-cutting edits in one PR.