Can we add CODEOWNERS file to define individuals or teams that are responsible for code in the repo/subdirectories?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- devops
Research direction
Start by reviewing GitHub's CODEOWNERS documentation and the referenced Application-Insights-Workbooks repository. Confirm the repository paths for AODS workbooks and alert ARM templates, identify the responsible individuals or teams, and consider the work done when those paths have defined owners for pull request approval.
Written by the indexing model from the issue text.
Description
Hello,
We are planning to put workbooks and alerts ARM templates that we are building for Azure Operator Distributed Services (AODS) customers in this repo. We want to have control on who can approve PRs for code change on AODS workbooks and alert templates. Can we add CODEOWNERS file to define individuals or teams that are responsible for code in the repo/subdirectories? For example something like this repo has: https://github.com/microsoft/Application-Insights-Workbooks
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AzureMonitorCommunity
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in microsoft/AzureMonitorCommunity
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100