ci: make the DevOps team code owner of the CI pipeline - #1069
Conversation
The .ci/ pipeline and the Blossom workflow that triggers it had no owner beyond the repository-wide list, so a change to either was only ever auto-requested from reviewers outside DevOps. Assign both to @NVIDIA/nbu-swx-cloudai-devops, synced from the Access-Github-nbu-swx-cloudai-devops DL. The repository-wide owners stay unchanged for everything else. Refs: HPCINFRA-4886 Signed-off-by: Or Balayla <obalayla@nvidia.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA/cloudai/.coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe CODEOWNERS file adds ownership rules for ChangesCI Path Ownership
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to This change only adds code owners for the CI paths, so it has no runtime impact. It requests reviews from the DevOps team on those paths. Whether approval is enforced depends on a repository ruleset outside this PR, which the author should confirm. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
@NVIDIA/nbu-swx-cloudai-devopsthe code owner of.ci/and.github/workflows/blossom-ci.yml, so changes to the CI pipeline and the workflow that triggers it are auto-requested from DevOps.Access-Github-nbu-swx-cloudai-devopsDL and already has Write on the repository, which GitHub requires for a code-owner team.*owners are unchanged. The new lines come after it, since the last matching pattern wins.Test Plan
pre-commit run --files .github/CODEOWNERSpasses.GitHub's CODEOWNERS validator on this PR's head reports no errors, so the team resolves and has the access it needs:
Additional Notes
CODEOWNERS only requests the review. "Require review from Code Owners" stays off in the
mainruleset, because with the*line it would make one of the four listed owners mandatory on every pull request. Approval for these paths will be enforced separately with a path-scoped Required reviewers rule in the ruleset.