Skip to content

chore(codeowners): add eng-devops as release.yaml owner#3916

Open
Piotr1215 wants to merge 1 commit into
mainfrom
devops-757/codeowners-release-pipelines
Open

chore(codeowners): add eng-devops as release.yaml owner#3916
Piotr1215 wants to merge 1 commit into
mainfrom
devops-757/codeowners-release-pipelines

Conversation

@Piotr1215
Copy link
Copy Markdown
Contributor

Summary

  • Add @loft-sh/eng-devops as a co-owner of .github/workflows/release.yaml, alongside the existing @loft-sh/eng-tech-leads.
  • Aligns vcluster with the DevOps team scope: explicit ownership of release pipelines only.

Why

DevOps is the team that operates the release pipeline; making them an explicit CODEOWNER of release.yaml ensures release-pipeline review/approval routes to them directly without depending on team membership in eng-tech-leads.

Test plan

  • CODEOWNERS syntax check (GitHub UI / actionlint)
  • Confirm a draft PR touching release.yaml requests review from @loft-sh/eng-devops

Refs DEVOPS-757

DevOps team should be explicit owners of release pipelines, in line
with the team scope (release CI/CD only). Add @loft-sh/eng-devops as
co-owner of release.yaml alongside the existing @loft-sh/eng-tech-leads
ownership so release-pipeline reviews route to DevOps directly.

Refs DEVOPS-757
@Piotr1215 Piotr1215 requested a review from a team as a code owner May 7, 2026 11:13
@Piotr1215 Piotr1215 requested a review from sydorovdmytro May 7, 2026 11:15
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

E2E Ginkgo Tests

Status Commit Run
Passed b97f64e3e8727989aefc3027623bf5785b9aadf1 View run #25492356533

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant