Enhance GitHub OAuth configuration instructions

[rainxchzed]

Expanded the GitHub OAuth configuration section with detailed steps for creating an OAuth app, copying the Client ID, and adding it to the project.

Summary by CodeRabbit

• Documentation
  • Expanded GitHub OAuth configuration guide: renamed the section and replaced brief guidance with a detailed, step‑by‑step setup (create OAuth app, obtain credentials, configure locally, sync/run) and an expanded notes section clarifying per‑developer app usage and that the client secret is not required.

[coderabbitai]

Walkthrough

The README's "Configuration" section was renamed to "🔑 Configuration (GitHub OAuth)" and replaced the prior concise guidance with a detailed 4-step GitHub OAuth setup guide (Create OAuth App, copy Client ID, add to project via local.properties, sync & run) and an expanded Notes section clarifying credential usage.

Changes

Cohort / File(s)	Summary
Documentation README.md	Renamed configuration heading and expanded the Configuration section into a 4-step GitHub OAuth setup guide with notes on per-developer OAuth apps, Client ID usage, and Client Secret not required.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 I hopped through lines of README bright,

Added steps to make OAuth right,
Client ID in place, secrets kept light,
Developers grin in morning light,
A tiny guide to set code tight.

🚥 Pre-merge checks | ✅ 3

✅ 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 'Enhance GitHub OAuth configuration instructions' directly and accurately summarizes the main change: expanding the GitHub OAuth configuration section with detailed setup instructions.
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.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rainxchzed-enhance-configure-project

---

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: 1

🤖 Fix all issues with AI agents

In `@README.md`:
- Around line 374-377: The README's "### ❗ Important Notes" section contains an
inconsistent Client Secret message: update the bullet "- Never share your
**Client Secret** publicly." to match the earlier statement that the Client
Secret is "❗ NOT required for this project" by either removing the warning or
rewording it to: "This project uses OAuth Device Code flow and does not require
a Client Secret; if you use a Client Secret in other contexts, never share it
publicly." Edit the "### ❗ Important Notes" section and the related Client
Secret sentence so both convey the same guidance and eliminate developer
confusion.

🧹 Nitpick comments (1)

README.md (1)

348-358: Consider clarifying the Homepage URL field.

The placeholder https://github.com/username/repo_name in the table might leave developers uncertain about what to enter. Consider adding a brief note that this can be any valid URL (e.g., "your fork's URL or any valid URL you control").

📝 Suggested clarification

 | Field                          | Value                                       |
 | ------------------------------ | ------------------------------------------- |
 | **Application name**           | Anything you like (e.g. *GitHub Store Dev*) |
-| **Homepage URL** | `https://github.com/username/repo_name`                   |
+| **Homepage URL** | `https://github.com/username/repo_name` (or any valid URL) |
 | **Authorization callback URL** | `githubstore://callback`                    |