Add CI workflow to validate website files

[RishiByte]

Added Workflow

Summary by CodeRabbit

• Chores
  • Added continuous integration workflow to automatically validate project structure on pull requests and commits to main branch.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
demondie	Ready	Preview, Comment	Jun 3, 2026 3:50pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR introduces a new GitHub Actions CI workflow that validates the website structure. The workflow triggers on pull requests and pushes to the main branch, running a single validation job that confirms required files (index.html and style.css) exist before reporting successful completion.

Changes

CI Website Validation Workflow

Layer / File(s)	Summary
Website validation workflow .github/workflows/ci.yml	Adds GitHub Actions workflow Website Check with a validate job that checks for required files index.html and style.css on pull requests and main-branch pushes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A workflow takes flight on the CI wind,
Checking files that must be pinned,
HTML and CSS in place so right,
Green checks glow in the pull request light! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add CI workflow to validate website files' directly and accurately describes the main change: adding a GitHub Actions CI workflow for file validation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch RishiByte-patch-3

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

16-20: ⚡ Quick win

Add descriptive error messages for missing files.

The test -f command fails silently without indicating which file is missing. Adding explicit error messages improves the developer experience when the workflow fails.

💬 Proposed improvement with better error messages

       - name: Check HTML exists
-        run: test -f index.html
+        run: test -f index.html || { echo "Error: index.html not found"; exit 1; }

       - name: Check CSS exists
-        run: test -f style.css
+        run: test -f style.css || { echo "Error: style.css not found"; exit 1; }

🤖 Prompt for 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.

In @.github/workflows/ci.yml around lines 16 - 20, The workflow steps "Check
HTML exists" and "Check CSS exists" use silent `test -f` checks; update their
run commands to detect missing files and print clear error messages (including
the filename and context) and exit non-zero so the job fails visibly.
Specifically, replace the current `test -f` invocations in the "Check HTML
exists" and "Check CSS exists" steps with a shell snippet that checks for the
file (index.html and style.css respectively), echoes a descriptive error to
stderr if it's missing (e.g., "index.html is missing: ensure build produced
it"), and exits with a non-zero status.

🤖 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/ci.yml:
- Line 14: Replace the floating actions/checkout@v4 usage with a pinned commit
SHA and disable credential persistence: update the workflow step that currently
says uses: actions/checkout@v4 to use a specific commit SHA
(actions/checkout@<full-commit-sha>) and add the with: persist-credentials:
false option so the checkout step does not leave credentials in the runner.

---

Nitpick comments:
In @.github/workflows/ci.yml:
- Around line 16-20: The workflow steps "Check HTML exists" and "Check CSS
exists" use silent `test -f` checks; update their run commands to detect missing
files and print clear error messages (including the filename and context) and
exit non-zero so the job fails visibly. Specifically, replace the current `test
-f` invocations in the "Check HTML exists" and "Check CSS exists" steps with a
shell snippet that checks for the file (index.html and style.css respectively),
echoes a descriptive error to stderr if it's missing (e.g., "index.html is
missing: ensure build produced it"), and exits with a non-zero status.

🪄 Autofix (Beta)

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

Review profile: CHILL

Plan: Pro

Run ID: 0ec37e58-6ed9-42a2-b9c8-f82496dc463b

📥 Commits

Reviewing files that changed from the base of the PR and between 82b2c9f and 606ad2d.

📒 Files selected for processing (1)

• .github/workflows/ci.yml