Monorepo Pull Request Template

Monorepo PR Template

Monorepos contain multiple packages, services, or applications in a single repository. Changes in one package can have cascading effects on others. This template helps contributors communicate the scope and impact of their changes across the monorepo.

Template Structure

## Description
<!-- Describe the changes. -->

## Affected Packages / Services
<!-- List the packages or services modified by this PR. -->
- [ ] packages/core
- [ ] packages/ui
- [ ] packages/api
- [ ] apps/web
- [ ] apps/mobile
- [ ] shared/config

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Dependency update
- [ ] Build / tooling change

## Cross-Package Impact
<!-- Do changes in one package affect others? List dependencies. -->

## Checklist
- [ ] Changes are scoped to the minimum set of packages
- [ ] Cross-package dependencies are updated
- [ ] Package-specific tests pass
- [ ] Integration tests pass
- [ ] Build for all affected packages succeeds
- [ ] No circular dependency introduced
- [ ] Version bumps applied (if using independent versioning)

## Testing
<!-- How were cross-package interactions tested? -->

## Related Issues
<!-- Closes #(issue number) -->

Package Scope Declaration

The Affected Packages section with checkboxes gives reviewers an immediate understanding of the PR's scope. A PR touching only packages/ui can be reviewed by the frontend team, while one touching packages/core might need broader review.

Cross-Package Impact Analysis

In monorepos, a change to a shared library (packages/core) can break consuming packages. The Cross-Package Impact section forces contributors to think about downstream effects and document them.

Independent vs. Unified Versioning

Some monorepos use independent versioning (each package has its own version), while others use unified versioning (all packages share one version). The checklist reminder about version bumps is relevant for independently versioned monorepos using tools like Changesets or Lerna.

Scoped Testing

The checklist asks for both package-specific tests and integration tests. In a monorepo, running the full test suite might be expensive, so targeted testing of affected packages is important.