Merge branch 'main' into codex/thiet-ke-lai-giao-dien-file-readme.md

[zskbot]

Summary

Closes #

• [] I have read the Contributing and the strict No-AI Policy guides.

How Did You Test this Change?

Images/Videos

---

[kilo-code-bot]

Kilo Code Review could not run — your account is out of credits.

Add credits or switch to a free model to enable reviews on this change.

[devin-ai-integration]

Devin Review found 5 potential issues.

[qodo-code-review]

PR Summary by Qodo

Redesign README and add IBM-terminal landing page + bundled docs

📝 Documentation ✨ Enhancement 🕐 20-40 Minutes

AI Description

• Redesign root README with Vietnamese-first, badge-heavy layout and streamlined sections.
• Replace Vite entry index.html with a static IBM-terminal styled landing page.
• Add bundled reference docs (Azure WebApp deploy, Refined GitHub, GitHub API guide).

Diagram

graph TD
  U(["Reader/Contributor"]) --> R["README.md"] --> DOCS["Bundled docs"]
  U --> IDX["index.html landing"] --> TW{{"Tailwind CDN"}} --> FNT{{"Google Fonts"}}
  DOCS --> AZ["Azure/README.md"] --> RG["Refined GitHub README"]
  DOCS --> Q["question/readme.md"]
  IDX --> DEMO["ai_studio_code.html"]
  subgraph Legend
    direction LR
    _u(["User"]) ~~~ _d["Doc/Page"] ~~~ _e{{"External"}}
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Keep Vite `index.html`; move IBM terminal page to `public/` or `docs/`

• ➕ Avoids breaking the React/Vite entrypoint (#root + src/main.tsx)
• ➕ Keeps demo/marketing page available without affecting app runtime
• ➕ Clear separation between app shell and standalone HTML mock
• ➖ Slightly less “immediate” if the static page was intended to be the app itself
• ➖ Requires deciding routing/hosting location for the standalone page

2. Implement the IBM-terminal layout inside React components

• ➕ Preserves the current build/runtime model (Vite + React)
• ➕ Enables real data wiring (PRs/issues/telemetry) rather than static mock content
• ➕ Keeps Tailwind usage consistent with app tooling instead of CDN injection
• ➖ More engineering effort than a static HTML drop-in
• ➖ Requires componentization and state/data integration work

3. Link to external upstream docs instead of copying vendor READMEs

• ➕ Reduces repo bloat and maintenance burden
• ➕ Avoids licensing/attribution ambiguity from vendored content
• ➕ Ensures docs stay current with upstream changes
• ➖ Requires network access; less convenient for offline reading
• ➖ External links can rot over time

Recommendation: If the React app is still intended to run, revert index.html back to the Vite/React entry (restore #root + module script) and place the IBM-terminal HTML as a separate demo page (e.g., public/ibm-terminal.html or under docs/). If the goal is to pivot to a purely static site, follow up by removing/adjusting the React entry (src/main.tsx, build scripts) and documenting that architectural change explicitly. For the large third-party READMEs, prefer linking or clearly labeling them as vendored with proper attribution.

Files changed (6) +918 / -177

Enhancement (2) +225 / -12

ai_studio_code.htmlAdd standalone IBM-terminal themed HTML mock page +113/-0

Add standalone IBM-terminal themed HTML mock page

• Adds a static Tailwind CDN-based HTML page styled like an IBM Carbon terminal dashboard, with mock log output, action tiles, and an input prompt. File currently lacks a trailing newline.

ai_studio_code.html

index.htmlReplace Vite/React entry HTML with static IBM-terminal landing page +112/-12

Replace Vite/React entry HTML with static IBM-terminal landing page

• Replaces the default Vite HTML shell ('#root' + 'src/main.tsx' module) with a static Tailwind CDN + Google Fonts page that renders an IBM-terminal styled dashboard. This likely changes the app’s runtime behavior by removing the React mount point and script reference; file also lacks a trailing newline.

index.html

Documentation (4) +693 / -165

README.mdAdd Azure WebApps deploy action documentation (vendored README) +278/-0

Add Azure WebApps deploy action documentation (vendored README)

• Introduces a new Azure deployment guide describing 'azure/webapps-deploy' workflows, credential setup, and sample YAML pipelines. This appears to be a copied upstream README intended as reference material inside the repo.

Azure/README.md

README.mdRedesign README with Vietnamese-first layout and streamlined sections +112/-165

Redesign README with Vietnamese-first layout and streamlined sections

• Reformats the README into a centered hero with larger badges and a Vietnamese-first narrative. Replaces the previous long/aspirational feature list with a tighter table of highlights, adds a clearer table of contents, and rewrites sections for install, preview, keybindings, configuration, troubleshooting, and contribution guidance.

README.md

README.mdAdd Refined GitHub extension README as bundled documentation +192/-0

Add Refined GitHub extension README as bundled documentation

• Adds a large documentation file describing installation and feature highlights of the Refined GitHub browser extension, including many images/links. File currently lacks a trailing newline.

chrome.google.com/webstore/detail/refined-github/README.md

readme.mdAdd GitHub API/community resource guide documentation +111/-0

Add GitHub API/community resource guide documentation

• Adds a curated resource guide for REST/GraphQL APIs, webhooks, OAuth/GitHub Apps auth, rate limiting, and open-source learning links. File currently lacks a trailing newline.

question/readme.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (3) 📘 Rule violations (0) 📜 Skill insights (0)

1. React entrypoint removed 🐞 Bug ≡ Correctness

Description

index.html no longer provides the #root mount node or loads /src/main.tsx, so the Vite/React
UI will not render and the app won’t boot when running npm run dev/build.

Code

index.html[L9-10]

-    <div id="root"></div>
-    <script type="module" src="/src/main.tsx"></script>

Evidence

The repo still contains a Vite/React entrypoint that mounts into #root, and Vite scripts are still
present; the current index.html contains neither the mount node nor a module script to load the
React entry.

src/main.tsx[1-10]
package.json[1-12]
index.html[1-55]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Vite/React app is no longer bootstrapped because `index.html` removed the `#root` element and the module script that loads `/src/main.tsx`.

## Issue Context
- `src/main.tsx` mounts React into an element with id `root`.
- The root `package.json` scripts use Vite, which uses `index.html` as its entrypoint.

## Fix
Choose one:
1) **Keep the React app**: restore `<div id="root"></div>` and `<script type="module" src="/src/main.tsx"></script>` in `index.html` and move the new static UI into React components.
2) **Switch to static HTML intentionally**: remove/disable the Vite+React entry (`src/main.tsx`, React deps, etc.) and update docs/scripts accordingly.

## Fix Focus Areas
- index.html[1-30]
- src/main.tsx[1-10]
- package.json[1-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Unpinned CDN script dependency 🐞 Bug ⛨ Security

Description

index.html executes Tailwind via https://cdn.tailwindcss.com, creating a runtime dependency on a
third-party script that can change independently of the repo and can fail/behave differently if
blocked or updated.

Code

index.html[R7-8]

+    <script src="https://cdn.tailwindcss.com"></script>
+    <link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@300;400;600&display=swap" rel="stylesheet">

Evidence

Both HTML files include the Tailwind CDN script, meaning page rendering depends on a third-party
executable script at runtime.

index.html[1-12]
ai_studio_code.html[1-9]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The HTML loads Tailwind’s CDN JavaScript at runtime (`https://cdn.tailwindcss.com`). This is an avoidable supply-chain/availability/reproducibility risk because the executed code is not pinned to a specific immutable artifact controlled by this repo.

## Issue Context
The repo already uses Vite and has Tailwind-related dependencies, so Tailwind can be built into the app instead of executed from a CDN.

## Fix
- Prefer bundling Tailwind during build (Vite + Tailwind pipeline) and remove the CDN `<script>`.
- If this page must stay static, pin/self-host the exact asset (and consider a strict CSP); avoid executing a moving CDN script.

## Fix Focus Areas
- index.html[1-15]
- ai_studio_code.html[1-15]
- package.json[13-37]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

3. Truncated README content 🐞 Bug ⚙ Maintainability

Description

chrome.google.com/webstore/detail/refined-github/README.md ends mid-URL, leaving broken Markdown
and indicating the file was likely copied incompletely.

Code

chrome.google.com/webstore/detail/refined-github/README.md[192]

+- [](# "align-issue-labels") [In issue/PR lists, aligns the labels to the left, below each title.](https://github.com/user-att

Evidence

The file’s final line is an incomplete Markdown link (https://github.com/user-att), showing it was
cut off.

chrome.google.com/webstore/detail/refined-github/README.md[186-192]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The newly added README appears truncated (it ends in the middle of a link), which breaks rendering and suggests an incomplete/failed copy.

## Issue Context
The file ends abruptly at line 192.

## Fix
- Re-copy/regenerate the README from its source to ensure it is complete.
- Ensure the file ends with a trailing newline.

## Fix Focus Areas
- chrome.google.com/webstore/detail/refined-github/README.md[186-192]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[devin-ai-integration]

Devin Review found 2 new potential issues.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (6 files)

• index.html
• ai_studio_code.html
• README.md
• chrome.google.com/webstore/detail/refined-github/README.md
• question/readme.md
• Azure/README.md