Create Azure/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

---

[chatgpt-codex-connector]

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

[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

[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: 32ff71ca-88f7-434b-afd7-9d4af789b38f

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]

PR Summary by Qodo

Add Azure Web Apps deploy guide and additional reference READMEs

📝 Documentation 🕐 10-20 Minutes

AI Description

• Add an Azure Web Apps GitHub Actions deployment guide with end-to-end workflow examples.
• Add reference READMEs for GitHub API learning resources and the Refined GitHub extension.
• Normalize the root README title casing for consistent project branding.

Diagram

graph TD
  R["Repository docs"] --> ROOT["README.md"] --> BRAND["Project title"]
  R --> AZ["Azure/README.md"] --> DEPLOY["WebApp deploy guide"]
  R --> Q["question/readme.md"] --> API["GitHub API resources"]
  R --> CH["chrome.../README.md"] --> EXT["Refined GitHub docs"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Move third-party-derived docs under a single /docs area with an index

• ➕ Improves discoverability and avoids scattered top-level folders
• ➕ Allows a single landing page to explain intent/scope of each document
• ➖ Requires reorganizing paths and possibly updating any external links

2. Link the new READMEs from the root README (table of contents)

• ➕ Makes new documentation immediately discoverable to users
• ➕ Minimal structural change; keeps files where they are
• ➖ Root README can become noisy if many reference docs are added over time

3. Replace large copied READMEs with short stubs linking to upstream sources

• ➕ Avoids content drift and licensing/attribution concerns
• ➕ Keeps the repo lightweight
• ➖ Less convenient for offline browsing and searching within the repo

Recommendation: If these documents are intended as long-lived repo documentation, add a short docs index (either in README.md or /docs/README.md) and link to Azure/question/chrome guides. If the content is primarily mirrored from upstream projects, consider replacing the large copies with brief stubs plus upstream links to reduce maintenance and drift.

Files changed (4) +582 / -1

Documentation (4) +582 / -1

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

Add Azure Web Apps deploy action guide and workflow examples

• Introduces a comprehensive README describing the Azure App Service GitHub Action, supported artifacts, and prerequisites. Includes sample GitHub Actions workflows (publish profile and service principal) plus credential configuration guidance.

Azure/README.md

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

Normalize project title casing in root README

• Updates the main heading from a stylized/emoji title to an uppercase title for consistency.

README.md

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

Add Refined GitHub extension README content

• Adds a detailed README for the Refined GitHub browser extension, including install links and a large feature highlights section. Note: the file currently ends without a trailing newline.

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

readme.mdAdd curated GitHub API and integration resource guide +111/-0

Add curated GitHub API and integration resource guide

• Adds a community-oriented resource list covering REST/GraphQL/Webhooks, auth (OAuth/GitHub Apps), rate limits, and related integrations. Note: the file currently ends without a trailing newline.

question/readme.md

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

[qodo-code-review]

Code Review by Qodo

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

1. Insecure workflow examples 🐞 Bug ⛨ Security

Description

Azure/README.md includes sample workflows that use a mutable ref (actions/checkout@master) and an
obsolete runtime (Node 10 via setup-node@v1). Users copying these examples can end up with
non-reproducible and potentially unsafe workflows, and the Node 10 example conflicts with this
repo’s documented Node >=18 requirement.

Code

Azure/README.md[R79-82]

+      uses: actions/checkout@master
+
+    - name: Setup Node 10.x
+      uses: actions/setup-node@v1

Evidence

The newly added Azure README explicitly instructs users to use actions/checkout@master and
actions/setup-node@v1 with Node 10.x, while the project documentation states Node >= 18 is
required.

Azure/README.md[66-85]
PROJECT-SUMMARY.md[7-12]

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` contains GitHub Actions workflow samples that recommend `actions/checkout@master` and `actions/setup-node@v1` with `node-version: '10.x'`. This encourages consumers of the documentation to use mutable/unpinned actions and an EOL Node version, and it’s inconsistent with the repo’s stated Node requirement.

### Issue Context
This is documentation (not an active workflow in this repo), but README examples are commonly copy/pasted into real CI, so they should model secure/reproducible patterns.

### Fix Focus Areas
- Azure/README.md[66-85]
- PROJECT-SUMMARY.md[7-12]

### What to change
- Replace `actions/checkout@master` with a stable version (e.g. `actions/checkout@v4`) or a pinned commit SHA.
- Replace `actions/setup-node@v1` + `node-version: '10.x'` with a supported version (e.g. `actions/setup-node@v4` and Node `18`/`20`, aligned with this repo’s documented requirement).
- Consider adding a short note recommending pinning third-party actions to commit SHAs for supply-chain hardening.

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

---

2. Wrong repository description 🐞 Bug ≡ Correctness

Description

Azure/README.md states that this repository “contains GitHub Action for Azure WebApp”, but the
repo’s own docs describe a React/Vite/TypeScript dashboard application. This makes the new
documentation misleading and likely to send contributors/users down an unrelated Azure Action path.

Code

Azure/README.md[R7-8]

+This repository contains GitHub Action for Azure WebApp to deploy to an Azure WebApp (Windows or Linux). The action supports deploying a folder, *\*.jar*, *\*.war*, and \**.zip* files (except msBuild generated packages).
+

Evidence

Azure/README.md claims the repo is an Azure WebApp deploy action and points to Azure/webapps-deploy,
while this repo’s documentation describes a React/Vite/TypeScript application.

Azure/README.md[5-15]
PROJECT-SUMMARY.md[1-11]
README-APP.md[1-5]

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` describes this repository as the Azure Web Apps deploy GitHub Action and links to the `Azure/webapps-deploy` repository, which does not match this repository’s purpose.

### Issue Context
The repo documentation (e.g. PROJECT-SUMMARY/README-APP) describes a React + Vite + TypeScript application. The Azure Action README appears to be unrelated, which can confuse maintainers and users.

### Fix Focus Areas
- Azure/README.md[5-15]
- PROJECT-SUMMARY.md[1-11]
- README-APP.md[1-5]

### What to change
- If the Azure folder is accidental/unrelated: remove `Azure/README.md`.
- If the intent is to document how to deploy *this* app to Azure: rewrite the README to describe this project (not `Azure/webapps-deploy`), and update links/examples accordingly (including Node version alignment).
- Avoid claiming “This repository contains GitHub Action …” unless the repo actually ships that action.

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

---

3. Truncated README file 🐞 Bug ≡ Correctness

Description

chrome.google.com/webstore/detail/refined-github/README.md ends mid-URL, leaving malformed Markdown
in the final list item. This indicates the file was added incomplete and will render broken
documentation as-is.

Code

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

+- [](# "sticky-conversation-list-toolbar") [Makes the issue/PR list’s filters toolbar sticky.](https://github-production-user-asset-6210df.s3.amazonaws.com/83146190/261164103-875b70f7-5adc-4bb2-b158-8d5231d47da2.gif)
+- [](# "sticky-comment-header") [Makes the comment header sticky when scrolling through long comments.](https://github.com/user-attachments/assets/0d6deca0-0f49-4aa3-ab23-0cfbde4fa4e8)
+- [](# "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 end of the file is visibly cut off mid-URL in the checked-in content, which will break rendering
of that last item.

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 added `chrome.google.com/webstore/detail/refined-github/README.md` is truncated at the end (it stops mid-link: `https://github.com/user-att`), producing invalid Markdown.

### Issue Context
This is a newly added file in the PR, so the truncation is PR-introduced and should be fixed before merge.

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

### What to change
- Restore the missing tail of the README so the final bullet/link is complete.
- Ensure the file ends with a newline.
- If this README is not intended to be part of the repo, remove the file/directory instead of keeping a partial copy.

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