[CI] ci: add GitHub Actions pipeline for lint, build, and test validation (#496) - #504
Closed
prince-pokharna wants to merge 1 commit into
Closed
Conversation
- Add .github/workflows/ci.yml with separate frontend and backend jobs - Frontend job: npm ci, lint (--if-present), build, test (--passWithNoTests) - Backend job: npm ci, lint (--if-present), test (--passWithNoTests) - Node 20, npm cache, works with monorepo structure (separate working-directory) - Add CI status badge to README.md Closes #496
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a GitHub Actions CI workflow to RIVETO, closing the infrastructure gap described in #496.
What's added
.github/workflows/ci.ymlTwo parallel jobs:
npm ci→ lint (--if-present) →npm run build→ test (--passWithNoTests)npm ci→ lint (--if-present) → test (--passWithNoTests)mainactions/checkout@v4+actions/setup-node@v4(Node 20)package-lock.jsonfor fast runs--if-present/--passWithNoTestsmakes it safe even if scripts aren't fully set up yetREADME.mdWhy separate jobs?
Running frontend and backend in parallel cuts CI time roughly in half and gives precise failure attribution per layer.
Testing this PR
The workflow will run automatically when this PR is opened. You can watch it at:
Actions→CItab.Closes #496