Commit Graph

2 Commits (gw/data-https-insecure-certificate)

Author SHA1 Message Date
Jason Stirnaman 303d3a5992
feat(github): reduce CODEOWNERS noise, add suggested reviewers to PR template (#6797)
CODEOWNERS changes:
- Remove engineering teams and PMs from auto-assignment
- Keep only @influxdata/docs-team as mandatory reviewer
- Reduces auto-assigned reviewers from 4+ to 1 per PR

PR template changes:
- Add collapsible "Suggested reviewers" section with tables by product
- Preserve all reviewer information from old CODEOWNERS
- Include engineering teams and PMs for manual assignment
- Add tips for draft PRs and Copilot workflow

Benefits:
- Eliminates notification spam for engineering/PM teams
- Authors manually request reviewers when ready
- Draft PRs no longer trigger unwanted notifications
- Reviewer information still easily accessible

https://claude.ai/code/session_0173AuWPoy6UXiatCMGz4W7h

Co-authored-by: Claude <noreply@anthropic.com>
2026-02-09 13:24:31 -06:00
Jason Stirnaman 8831624750
chore(repo): add CODEOWNERS file for automated review assignments (#6752)
* chore(repo): add CODEOWNERS file for automated review assignments

Add .github/CODEOWNERS file to define code ownership and automate
reviewer assignments for pull requests across the documentation repository.

Changes:
- Create .github/CODEOWNERS with comprehensive ownership definitions
- Implement three-tier review approach: engineering + specific PMs + docs team
- Use 6 engineering teams, 7 specific product managers, and 1 docs team
- Define default ownership (@influxdata/docs-team) for all files
- Add product-specific ownership with specific PM assignments based on official responsibility matrix
- Assign infrastructure ownership (@influxdata/docs-team) for CI/CD, build configs, and tooling
- Require docs team review for agent-modified files (AGENTS.md, CLAUDE.md, copilot-instructions.md, etc.)
- Add TODO note about distributing API specs into content directories

Coverage includes:
- 14 product-specific content paths with tiered team review
- 8 product-specific api-docs subdirectories assigned to respective owners
- 6 engineering teams for technical accuracy
- 7 specific product managers assigned by product responsibility
- 1 documentation team for content quality
- Infrastructure and tooling (CircleCI, GitHub workflows, layouts, assets, scripts)
- Build configuration files (package.json, Docker files, Vale configs)
- AI agent instruction files requiring careful oversight

Three-tier review approach:
1. Engineering teams verify technical accuracy and implementation details
2. Specific product managers (primary + secondary) ensure product strategy and feature alignment
3. Documentation team maintains content quality, style, and user experience

Engineering teams included:
- @influxdata/monolith-team (InfluxDB 3 Core, Enterprise)
- @influxdata/cloud-single-tenant (InfluxDB 3 Cloud Dedicated)
- @influxdata/platform-team (InfluxDB 3 Clustered)
- @influxdata/telegraf-team (Telegraf)
- @influxdata/bonitoo (Kapacitor, Chronograf, client libraries)
- @influxdata/edge (InfluxDB v1/v2 OSS, Enterprise v1)

Product managers assigned by responsibility area:
- @peterbarnett03 (Pete) - InfluxDB 3 Core, Enterprise (primary); Explorer (secondary)
- @garylfowler (Gary) - InfluxDB 3 Core, Enterprise, Cloud Serverless (secondary)
- @ritwika314 (Ritwika) - InfluxDB 3 Clustered, Cloud Dedicated (primary)
- @sanderson (Scott) - InfluxDB Cloud TSM, v1/v2, Enterprise v1, Telegraf, Kapacitor, Flux (primary); Clustered, Cloud Dedicated (secondary)
- @mavarius (Daniel) - InfluxDB Cloud TSM, Cloud Serverless, Explorer, Chronograf (primary)
- @jstirnaman (Jason) - InfluxDB Cloud TSM, v1/v2, Enterprise v1, Kapacitor, Flux (secondary)
- @caterryan (Ryan) - Telegraf, Chronograf (secondary)

Benefits:
- Technical accuracy from engineering teams who build the products
- Product alignment from specific PMs with official product responsibility
- Documentation quality from dedicated docs team
- Accountability through specific PM assignments per product
- Scalable with multiple team members preventing bottlenecks
- Comprehensive with three expert perspectives on product content

Implementation follows GitHub CODEOWNERS syntax with proper precedence
ordering (more specific patterns appear later to override general patterns).

API documentation: Product-specific /api-docs/ subdirectories are assigned to
their respective product owners and grouped with corresponding content paths.
General /api-docs/ tooling remains with docs team.

Resolves #6691

---

Validation plan (post-merge):
1. Create test PR modifying content/influxdb3/core/ file
2. Verify GitHub auto-requests review from @influxdata/monolith-team, @peterbarnett03, @garylfowler, and @influxdata/docs-team
3. Create test PR modifying content/influxdb3/explorer/ file
4. Verify GitHub auto-requests review from @mavarius and @peterbarnett03
5. Create test PR modifying content/influxdb/cloud/ file
6. Verify GitHub auto-requests review from @sanderson, @mavarius, and @jstirnaman
7. Test infrastructure changes request only @influxdata/docs-team
8. Verify any team member or specific PM can be assigned as reviewer
9. Test precedence with multi-path PR

* Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update .github/CODEOWNERS

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2026-01-20 12:22:22 -06:00