getsentry / getsentry/sentry

CODEOWNERS fails to notify on failure to sync

Open
#90,141 12 comments 2 reactions 0 assignees View on GitHub
Improvement Product Area: Settings - Repositories
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

Hey, we use CODEOWNERS integration with teams mapping and auto-assigning. It is very easy to miss syncing issues: some time ago, we made some group changes, and syncing stopped working because of missing mapping rules. We discovered that accidentally after 3 months (!). During this period, developers pushed new CODEOWNERS changes and did not understand why they sometimes did not work correctly

### Solution Brainstorm

Having simple notifications, alerts, and status info about CODEOWNERS syncing will be nice: by slack or just via email. Then, proper persons can quickly fix missing mappings or CODEOWNERS file format

### Product Area

Settings - Repositories

Contributor guide

Open the contributing guide

Research direction

The issue does not name files, tests, or entry points. Start by locating the CODEOWNERS integration sync flow, teams mapping rules, and repository Settings area; clarify whether the intended outcome is Slack or email notifications, status information, or both, and define the failure cases that must be reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.