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

[zskbot]

build các nút bấm và menu nền chuyển động logo nhà tài trợ màn hình giả lập thực thi dòng lệnh hình ảnh svg chuyển động

---

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 18ab0025-4b09-41ca-83dd-df5c907b8340

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[qodo-code-review]

ⓘ Your Qodo trial ends soon. Ask your workspace admin to set up billing to keep reviews running after the trial. Manage billing

[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 2 potential issues.

[qodo-code-review]

PR Summary by Qodo

Add multiple documentation READMEs and normalize project heading

📝 Documentation 🕐 10-20 Minutes

AI Description

• Add new Markdown docs for Azure Web App deployment via GitHub Actions.
• Add bundled README content for Refined GitHub and community/API resources.
• Standardize the root README project title casing.

Diagram

graph TD
  R["Repository docs"] --> M["README.md"] --> A["Azure/README.md"] --> C["chrome.../README.md"] --> Q["question/readme.md"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Link to upstream docs instead of copying

• ➕ Avoids maintaining large third-party text in this repo
• ➕ Upstream fixes/updates are automatically reflected
• ➕ Reduces repository size and merge conflicts
• ➖ Docs become unavailable if upstream moves/breaks links
• ➖ Harder to customize content for this repo’s specific needs

2. Move bundled docs under a single /docs directory with an index

• ➕ Clear ownership and discoverability of documentation
• ➕ Easier navigation via a docs landing page
• ➕ Reduces clutter of vendor-like paths in the repo root
• ➖ Requires reorganizing paths and updating any references
• ➖ Slightly more work now vs. accepting files as-is

3. Treat third-party content as vendored (LICENSE/ATTRIBUTION + pinned version note)

• ➕ Clarifies provenance and update policy
• ➕ More compliant if content is copied from external projects
• ➖ Still requires periodic manual updates
• ➖ Adds process overhead for doc updates

Recommendation: If these Markdown files are intended as long-lived internal docs, keeping them in-repo is fine, but consider consolidating them under /docs with a small index page. If they’re primarily third-party documentation copied verbatim (Azure action/Refined GitHub/community guides), prefer linking to upstream or explicitly marking them as vendored with attribution and a pinned source/version to reduce maintenance risk.

Files changed (4) +582 / -1

Documentation (4) +582 / -1

README.mdAdd Azure Web App deploy action README and workflow examples +278/-0

Add Azure Web App deploy action README and workflow examples

• Introduces a full README describing GitHub Actions deployment to Azure Web Apps, including prerequisites, publish profile vs. service principal authentication, and multiple end-to-end workflow templates.

Azure/README.md

README.mdNormalize root README title casing +1/-1

Normalize root README title casing

• Changes the project heading from a stylized/emoji title to an uppercase title while keeping the rest of the introduction intact.

README.md

README.mdAdd Refined GitHub extension README content +192/-0

Add Refined GitHub extension README content

• Adds a large README describing the Refined GitHub browser extension, including install links, sponsor section, and a long feature highlights list.

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

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

Add GitHub API/community resource guide

• Adds a curated guide for common community questions, covering REST/GraphQL resources, PATs, webhooks, OAuth/GitHub Apps, rate limits, and open source getting-started links.

question/readme.md

[qodo-code-review]

Code Review by Qodo

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

1. Unpinned action references 🐞 Bug ⛨ Security

Description

Azure/README.md includes workflow examples that use mutable action refs like actions/checkout@master
and actions/setup-node@v1, which are not immutable and can change unexpectedly if copy/pasted into
real workflows. This is inconsistent with the repository’s own workflows, which pin actions to
released versions (e.g., actions/checkout@v4).

Code

Azure/README.md[R78-80]

+    - name: 'Checkout Github Action' 
+      uses: actions/checkout@master
+

Evidence

The added Azure README explicitly uses actions/checkout@master/actions/setup-node@v1 in example
workflows, while the repo’s own lint workflow uses a released pinned tag (actions/checkout@v4).

Azure/README.md[76-85]
Azure/README.md[108-114]
Azure/README.md[158-166]
.github/workflows/lint.yml[12-16]

Agent prompt

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

## Issue description
`Azure/README.md` shows GitHub Actions examples using mutable references like `actions/checkout@master` and `actions/setup-node@v1`. This weakens supply-chain integrity and reproducibility for users who copy these snippets.

## Issue Context
Elsewhere in this repo, workflows use released version tags like `actions/checkout@v4`, which is the safer project convention.

## Fix Focus Areas
- Azure/README.md[76-85]
- Azure/README.md[108-114]
- Azure/README.md[158-166]
- .github/workflows/lint.yml[12-16]

## Suggested change
- Replace `actions/checkout@master` with `actions/checkout@v4` (or pin to a specific commit SHA if you want maximal hardening).
- Replace `actions/setup-node@v1` with a current major (e.g. `actions/setup-node@v4`) and update the Node version in the example accordingly.

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

---

2. Truncated README entry 🐞 Bug ≡ Correctness

Description

chrome.google.com/webstore/detail/refined-github/README.md ends with a truncated URL
(https://github.com/user-att) without closing the Markdown link, leaving the final list item
broken and the file incomplete. Readers will see a corrupted last entry and may miss intended
content.

Code

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

+- [](# "conversation-authors") [Highlights issues/PRs opened by you or the current repo’s collaborators.](https://github-production-user-asset-6210df.s3.amazonaws.com/83146190/252804821-a412e05c-fb76-400b-85b5-5acbda538ab2.png)
+- [](# "align-issue-labels") [In issue/PR lists, aligns the labels to the left, below each title.](https://github.com/user-att

Evidence

The final bullet line is cut off mid-URL and the file ends immediately after, confirming the
Markdown is incomplete.

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 file `chrome.google.com/webstore/detail/refined-github/README.md` ends with an incomplete Markdown link/URL (`https://github.com/user-att`) and no closing `)`.

## Issue Context
This appears to be a truncated copy/paste/merge result; the last bullet is cut off.

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

## Suggested change
- Replace the truncated URL with the full intended link and close the Markdown parentheses.
- Ensure the file ends cleanly after the last section (and add a trailing newline).

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

---

3. Broken markdown link 🐞 Bug ≡ Correctness

Description

Azure/README.md contains an invalid Markdown link for the Contributor role due to an extra opening
parenthesis, so the link won’t render correctly. This breaks the documentation at that location.

Code

Azure/README.md[R187-189]

+The previous sample workflow depends on user-level credentials stored as a [secret](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets) named `AZURE_CREDENTIALS` in your repository. The value of this secret is expected to be a JSON object that represents a service principal (an identifer for an application or process) that authenticates the workflow with Azure.
+
+To function correctly, this service principal must be assigned the [Contributor]((https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#contributor)) role for the web app or the resource group that contains the web app.

Evidence

The added README line contains the malformed (( sequence in the link target, which is not valid
Markdown link syntax.

Azure/README.md[187-190]

Agent prompt

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

## Issue description
In `Azure/README.md`, the Contributor role link is malformed as `[Contributor]((https://...))` (double `(`). This prevents proper Markdown rendering.

## Issue Context
This is within the newly added documentation section describing required Azure RBAC role.

## Fix Focus Areas
- Azure/README.md[187-190]

## Suggested change
Change:
- `[Contributor]((https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#contributor))`
To:
- `[Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#contributor)`

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