Move REVIEW.md to .cursor/BUGBOT.md (#2021)

* Move REVIEW.md to .cursor/BUGBOT.md

Signed-off-by: Evans Mungai <evans@replicated.com>

* Comment update

Signed-off-by: Evans Mungai <evans@replicated.com>

---------

Signed-off-by: Evans Mungai <evans@replicated.com>
This commit is contained in:
Evans Mungai
2026-04-16 15:40:45 +01:00
committed by GitHub
parent a3c453d1d6
commit 845fdcc8c8
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -19,4 +19,4 @@
- **Dedicated documentation needs** — For large or complex changes, consider whether CLI users or SDK consumers need standalone documentation (migration guides, new feature walkthroughs, updated examples).
- **Backwards compatibility** — Spec changes must consider existing specs in the wild. New fields should have sensible zero-value defaults. Removed fields should not cause parse failures.
- **Downstream impact on sbctl** — Changes to public Go packages (`pkg/collect`, `pkg/analyze`, API types, etc.) may require follow-up changes in [replicatedhq/sbctl](https://github.com/replicatedhq/sbctl), which imports this project as a dependency. Flag any breaking or behavioral changes that could affect sbctl.
- **Repository docs** — If your changes affect build commands, architecture, project conventions, or review guidelines, update `CLAUDE.md`, `README.md`, and `REVIEW.md` accordingly.
- **Repository docs** — If your changes affect build commands, architecture, project conventions, or review guidelines, update `CLAUDE.md`, `README.md`, and this file accordingly.
+1 -1
View File
@@ -27,4 +27,4 @@ Collectors live in `pkg/collect/`, analyzers in `pkg/analyze/`. When adding eith
## Code Review
See [REVIEW.md](REVIEW.md) for the full review checklist covering basic checks (API breaks, pattern violations, security, test coverage) and advanced checks (cross-feature impact, CLI vs SDK consumers, documentation needs).
See [.cursor/BUGBOT.md](.cursor/BUGBOT.md) for the full review checklist covering basic checks (API breaks, pattern violations, security, test coverage) and advanced checks (cross-feature impact, CLI vs SDK consumers, documentation needs).