[Bug] Lint and Test Workflows Failing on Markdown-Only PRs

[Limeload]

Issue: Lint and Test Workflows Failing on Markdown-Only PRs

Description

Currently, the CI workflows (Ruby on Rails CI / lint and test) are failing even on documentation-only pull requests that modify only Markdown (.md) files.
Ideally, these checks should pass or be skipped when no Ruby or code-related changes are made.

---

Steps to Reproduce

1. Open a pull request that only updates Markdown files (e.g., README.md or CONTRIBUTING.md).
2. Wait for GitHub Actions to run.
3. Observe that lint/test checks fail, even though no code was changed.

---

Expected Behavior

• Lint and test workflows should either pass automatically or be skipped for non-code (Markdown-only) PRs.

---

Actual Behavior

• The Ruby on Rails CI workflows (lint and test) still run and fail on doc-only PRs.
• This blocks merging even when no code is affected.

---

Possible Solutions

• Update the GitHub Actions configuration to:
  • Run lint/test jobs only when code files are changed (e.g., **/*.rb, Gemfile, etc.).
  • Skip these jobs when changes are limited to Markdown or documentation files.
• Add a separate job for docs validation (optional).

---

Affected Workflows

• .github/workflows/rails-lint.yml
• .github/workflows/rails-test.yml

---

Additional Context

This will streamline contributor experience and prevent unnecessary workflow failures for doc-related pull requests.

---

[github-actions]

🎯 Issue Assigned

Excellent! This issue has been assigned to @Limeload. You're now ready to start working on it! 🎉

Your next steps:

1. 🔗 Link your PR: When you create your pull request, include Closes #30 or Fixes #30 in the PR description to automatically link it to this issue.

2. ⏰ Timeline reminder: You have 2 days from now to complete your work and submit a PR. The deadline is 10/6/2025.

3. ✅ Quality checks: Before requesting a review, make sure your PR passes all automated checks:

   • TypeScript compilation
   • ESLint linting
   • Build verification
   • Security audit

4. 📝 Communication: If you encounter any blockers or need clarification, please comment on this issue. We're here to help!

5. 🚀 Ready to start: You can now begin working on this issue. Good luck!

Pro tip: You can track your progress by updating this issue with status comments as you work.

---

This is an automated reminder to help maintain our workflow standards.

[github-actions]

📋 Issue Guidelines

Hi @Limeload! Thanks for opening this issue. We appreciate your contribution to the project! 🚀

Please note the following workflow guidelines:

• 🎯 First-come, first-serve basis: Issues are assigned based on who expresses interest first. Please comment on the issue to show your interest before starting work.

• ⏳ Wait for assignment: Please do not start working until a maintainer has officially assigned this issue to you. This prevents duplicate work and ensures proper coordination.

• 🔗 Link your PR: Once assigned, when you create your pull request, make sure to link it to this issue using Closes #30 or Fixes #30 in your PR description.

• ⏰ 2-day timeline: Aim to complete your work and submit a PR within 2 days of assignment. If you need more time, please comment on this issue to discuss an extension.

• ✅ CI checks must pass: Before requesting a review, ensure your PR passes all automated checks (TypeScript, linting, build, security). You can see the status in the PR checks section.

Need help? Feel free to ask questions in the comments or reach out to maintainers.

---

This is an automated message to help maintain our workflow standards.

[Parthav46]

@Limeload, I would like to work on this issue if you are not already working on it. Can you please assign it to me?

[Limeload]

@Parthav46 Thank you for showing interest. As I'm already working on this, could you please pick an unassigned issue.