# `cc`

The `cc` field allows you to notify additional people on a pull request without requiring their approval. This is useful for keeping stakeholders informed or including subject matter experts who should be aware of changes but don't need to formally review them.

People listed in `cc` will be added as requested reviewers on GitHub, but their approval is not required for the scope to pass.

```toml
[[scopes]]
name = "frontend"
paths = ["src/frontend/**"]
reviewers = ["frontend-team"]
cc = ["product-manager", "designer"]
```

## When to use `cc`

- **Stakeholder awareness**: Keep project managers, product owners, or designers informed of relevant changes
- **Subject matter experts**: Include domain experts who should be aware but aren't primary reviewers
- **Cross-team coordination**: Notify other teams of changes that might affect their work
- **Documentation**: Include technical writers for documentation changes

## Combining with aliases

Like other reviewer fields, `cc` supports [aliases](../aliases.md):

```toml
[aliases]
stakeholders = ["product-manager", "designer", "tech-writer"]
security-team = ["security-lead", "security-engineer"]

[[scopes]]
name = "authentication"
paths = ["src/auth/**"]
reviewers = ["backend-team"]
cc = ["$security-team", "$stakeholders"]
```

## Differences from `reviewers`

| Field | Purpose | Required for approval | GitHub behavior |
|-------|---------|----------------------|-----------------|
| `reviewers` | Primary code reviewers | ✅ Yes | Added as requested reviewers |
| `cc` | Notification only | ❌ No | Added as requested reviewers |

## Example: Multi-team notification

```toml
[aliases]
mobile-team = ["alice", "bob"]
api-team = ["charlie", "diana"]
qa-team = ["eve", "frank"]

[[scopes]]
name = "mobile-api"
paths = ["src/mobile-api/**"]
reviewers = ["$api-team"]
cc = ["$mobile-team", "$qa-team"]
# API team must approve, mobile and QA teams are notified
```