feat: add GitHub Actions workflow for deploying to GitHub Pages and u…

[rahul-vyas-dev]

Additional Notes:

This PR adds CD action to have the hosted preview of the Development Environment.

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

• New Features

  • Added automated deployment to GitHub Pages when changes are pushed to the main branch.
  • Added the ability to trigger deployments manually.

• Improvements

  • Added standard commands for starting, building, and previewing the project locally.
  • Updated the build environment to use Node.js 22.

[coderabbitai]

Walkthrough

The project now provides Vite development, build, and preview commands. A GitHub Actions workflow builds the project with Node.js 22 and deploys the dist artifact to GitHub Pages.

Changes

GitHub Pages deployment

Layer / File(s)	Summary
Vite build and Pages deployment .github/workflows/CD.yml, package.json	The package scripts define Vite development, build, and preview commands. The workflow builds the project and deploys the dist artifact to GitHub Pages on pushes to main or manual dispatch.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: reach2saksham

Poem

A rabbit sees the Vite build run,
Then hops where Pages shine in sun.
The workflow carries dist with care,
To make the project bloom out there.
Hop, build, deploy!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: adding a GitHub Actions workflow to deploy the project to GitHub Pages.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/CD.yml:
- Line 25: Pin every listed GitHub Action in .github/workflows/CD.yml to its
approved full commit SHA instead of mutable version tags: lines 25
(actions/checkout), 28 (actions/setup-node), 34 (actions/configure-pages), 43
(actions/upload-pages-artifact), and 58 (actions/deploy-pages). Update each uses
reference while preserving the existing action versions and workflow behavior.
- Line 40: Update the Vite configuration’s defineConfig base setting to
/SupportUsButton/ for the GitHub Pages project deployment, ensuring generated
asset URLs resolve under the repository path while preserving root-base behavior
only for user or organization sites and custom domains.
- Around line 10-13: Update the workflow-level permissions to retain only
contents: read, and define pages: write and id-token: write under
jobs.deploy.permissions. In the build job’s checkout step, set
persist-credentials to false so deployment credentials are not retained during
npm ci or vite:build.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 612d91da-4878-412f-9de6-2c16e0eb4477

📥 Commits

Reviewing files that changed from the base of the PR and between ede74d7 and ef62aff.

📒 Files selected for processing (2)

• .github/workflows/CD.yml
• package.json