Add akram to OWNERS list

[akram]

Purpose of this PR

Proposed changes:

• <Change 1>
• <Change 2>
• <Change 3>

Change Category

• Bugfix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that could affect existing functionality)
• Documentation update

Rationale

Checklist

• I have conducted a self-review of my own code.
• I have updated documentation accordingly.
• I have added tests that prove my changes are effective or that my feature works.
• Existing unit tests pass locally with my changes.

Additional Notes

Summary by CodeRabbit

• Chore
  • Updated the approvers list in project configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The OWNERS file has been updated to add "akram" to the approvers list. No other changes were made to the file or codebase. This is a purely administrative modification to project governance.

Changes

Cohort / File(s)	Change Summary
Project governance OWNERS	Added "akram" to the approvers list

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A new approver joins the fray,
With akram leading the way,
The OWNERS list grows strong and true,
More guardians to see things through!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add akram to OWNERS list' is clear, specific, and directly matches the primary change in the pull request - adding a new approver to the OWNERS file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

OWNERS (1)

8-8: Verify authorization and consider alphabetical ordering.

The addition is syntactically correct. However:

1. Authorization: Since you're self-adding as an approver, please confirm this change has been reviewed and approved by existing project maintainers.

2. Optional: Alphabetical ordering: Consider sorting the approvers list alphabetically for better maintainability. Currently "akram" would appear first alphabetically.

🔎 Optional: Alphabetically sorted approvers list

 approvers:
+  - akram
   - andreyvelich
   - ChenYi015
   - jacobsalway
   - mwielgus
   - vara-bonthu
   - yuchaoran2011
-  - akram

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8714a45 and 997b59f.

📒 Files selected for processing (1)

• OWNERS (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: e2e-test (v1.31.4)
• GitHub Check: e2e-test (v1.24.17)
• GitHub Check: e2e-test (v1.32.0)
• GitHub Check: e2e-test (v1.29.12)
• GitHub Check: e2e-test (v1.30.8)
• GitHub Check: e2e-test (v1.27.16)
• GitHub Check: e2e-test (v1.26.15)
• GitHub Check: e2e-test (v1.28.15)
• GitHub Check: e2e-test (v1.25.16)
• GitHub Check: code-check
• GitHub Check: build-spark-operator
• GitHub Check: build-helm-chart

[shruthis4]

I think this list is for upstream branch, I dont see none of our team here

[shruthis4]

Closing it as we dont need to do this for CR approvals

[shruthis4]

Not needed for now