Skip to content

Add CODEOWNERS file #651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Punitkumar756 wants to merge 4 commits into from
+1,288 −43
Closed

Add CODEOWNERS file #651

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f39c48a
docs: enhance README with updated project description and features
Dec 13, 2025
28ac23c
docs: fix typo in onboarding guide
Dec 13, 2025
23557b8
docs: update README with essential requirements and quick start guide…
Dec 13, 2025
c092669
docs: update README and add troubleshooting guide for common issues
Dec 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# See https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
# This file designates users or teams responsible for code in the repository.
# Example:
# * @github-username

* @your-github-username
Copy link

Copilot AI Dec 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The placeholder username "@your-github-username" should be replaced with actual maintainer GitHub usernames. Based on the README.md, the maintainers are @jddeep and @chandansgowda. Consider using:
* @jddeep @chandansgowda

This ensures that pull requests are automatically assigned to the correct reviewers.

Suggested change
* @your-github-username
* @jddeep @chandansgowda

Copilot uses AI. Check for mistakes.
2 changes: 1 addition & 1 deletion ONBOARDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Onboarding Guide

Client side set up is straight forward and standard, i.e clone the repo [Resonte Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project etc so this guide would focus on the backend env set up.
Client side set up is straight forward and standard, i.e clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project etc so this guide would focus on the backend env set up.
Copy link

@coderabbitai coderabbitai bot Dec 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

Address grammar issues alongside the typo fix.

While correcting the "Resonate" typo, the sentence has three additional grammar issues that should be fixed:

  • Client side → client-side (compound adjective requires hyphen)
  • straight forward → straightforward (single word)
  • etc so → etc. so (abbreviation requires period)

Apply this diff to fix all issues:

-Client side set up is straight forward and standard, i.e clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project etc so this guide would focus on the backend env set up.
+Client-side setup is straightforward and standard; i.e., clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project, etc., so this guide would focus on backend environment setup.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Client side set up is straight forward and standard, i.e clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project etc so this guide would focus on the backend env set up.
Client-side setup is straightforward and standard; i.e., clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org/Resonate), do `flutter pub get` in the root of the project, etc., so this guide would focus on backend environment setup.
🧰 Tools
🪛 LanguageTool

[grammar] ~3-~3: Use a hyphen to join words.
Context: # Onboarding Guide Client side set up is straight forward and stan...

(QB_NEW_EN_HYPHEN)

[grammar] ~3-~3: Use a hyphen to join words.
Context: ...ard, i.e clone the repo [Resonate Client Side Repo](https://github.com/AOSSIE-Org...

(QB_NEW_EN_HYPHEN)

[style] ~3-~3: In American English, abbreviations like “etc.” require a period.
Context: ...ter pub get` in the root of the project etc so this guide would focus on the backen...

(ETC_PERIOD)

🤖 Prompt for AI Agents 
In ONBOARDING.md around line 3, update the sentence to fix grammar and the
"Resonate" typo: change "Client side" to "client-side", "straight forward" to
"straightforward", and add a period after "etc" so it reads "etc. so"; ensure
the sentence remains natural (e.g., "The client-side setup is straightforward
and standard, i.e., clone the repo Resonate Client Side Repo, run flutter pub
get in the root of the project, etc. so this guide focuses on the backend env
setup.").

Copy link

Copilot AI Dec 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a spelling error in "Resonte" which should be "Resonate".

Copilot uses AI. Check for mistakes.

Please strictly stick to the guide do not go off installing stuff on your own

Expand Down
Loading