docs:codeowners fixes #633

[Anushreebasics]

fixes #633

Adds a CODEOWNERS file to automatically request reviews from designated maintainers/teams when PRs modify specific files or directories.

@M4dhav kindly tag the other reviewers so that I can add them as well

Summary by CodeRabbit

• Chores
  • Added repository code ownership configuration.
  • Assigned ownership across repository areas: global, mobile app, documentation, CI/workflows, and backend.
  • Applied explicit protection for the code ownership file itself.
  • Clarifies review and approval routing and responsibility for changes.

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

[github-actions]

🎉 Welcome @Anushreebasics!
Thank you for your pull request! Our team will review it soon. 🔍

• Please ensure your PR follows the contribution guidelines. ✅
• All automated tests should pass before merging. 🔄
• If this PR fixes an issue, link it in the description. 🔗

We appreciate your contribution! 🚀

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a .github/CODEOWNERS file mapping repository paths and file globs to teams and individuals (global *, Flutter lib/ and *.dart, documentation docs/ and *.md, GitHub configs .github/, backend functions/, and the CODEOWNERS file itself).

Changes

Cohort / File(s)	Summary
New CODEOWNERS file \.github/CODEOWNERS	New file added specifying code owners: global owners (* -> AOSSIE-Org/maintainers, M4dhav), Flutter (lib/, *.dart -> AOSSIE-Org/flutter-team), docs (docs/, *.md -> AOSSIE-Org/maintainers), GitHub configs (.github/ -> AOSSIE-Org/devops), backend (functions/ -> AOSSIE-Org/backend-team), and explicit owner for .github/CODEOWNERS (AOSSIE-Org/maintainers).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I bounced through paths with eager cheer,

Placed each owner so PRs draw near,
A hop for docs, a nibble for code,
Reviewers aligned down every road,
From my burrow—organized and clear!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs:codeowners fixes #633' clearly references the CODEOWNERS file addition and issue #633, accurately summarizing the main change.
Linked Issues check	✅ Passed	The PR successfully implements the primary requirement from issue #633 by adding a CODEOWNERS file with appropriate team and maintainer assignments.
Out of Scope Changes check	✅ Passed	All changes are directly related to the linked issue #633; only the CODEOWNERS file was added with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 05ae83f and 8c9f711.

📒 Files selected for processing (1)

• .github/CODEOWNERS

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/CODEOWNERS

---

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.}

[Copilot]

Pull request overview

This PR adds a CODEOWNERS file to automatically request reviews from designated maintainers and teams when pull requests modify specific files or directories, addressing issue #633.

Key Changes:

• Introduces a CODEOWNERS file with ownership rules for various project components including Flutter code, documentation, GitHub workflows, and backend functions
• Establishes global maintainers as default owners for all files with specialized teams for specific areas

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6cd109b and c21a50f.

📒 Files selected for processing (1)

• .github/CODEOWNERS

🔇 Additional comments (1)

.github/CODEOWNERS (1)

1-23: CODEOWNERS structure looks good overall.

The file correctly designates team and individual owners across different repository areas (Flutter, backend, DevOps, etc.), and appropriately protects the CODEOWNERS file itself. Once the documentation ownership duplication is resolved, this will be ready.

[M4dhav]

Just add me as the maintainer for all sections for now

[Anushreebasics]

@M4dhav please check now

[M4dhav]

Comment out references to /maintainers and other groups for now, until I talk to Bruno about this

[Anushreebasics]

@M4dhav please check now

[M4dhav]

Syntax for comments in CODEOWNERS is #

[Anushreebasics]

@M4dhav sorry for the misunderstanding

[M4dhav]

Thank you for the contribution

[github-actions]

✅ PR Closed - Thank You, @Anushreebasics!

• If this PR was merged: Congratulations! Your contribution is now part of the project. 🚀
• If this PR was closed without merging: Don’t worry! You can always improve it and submit again. 💪

We appreciate your effort and look forward to more contributions from you! 🤝