Add Node.js CI workflow#2474
Open
darkdream123 wants to merge 1 commit into
Open
Conversation
This workflow sets up a CI pipeline for Node.js applications, including installation of dependencies, building the code, and running tests across multiple Node.js versions.
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow intended to run Node.js CI (install deps, build, and run tests) on pushes and pull requests.
Changes:
- Introduces a new
Node.js CIGitHub Actions workflow. - Configures a Node.js version matrix for CI runs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+22
to
+31
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Use Node.js ${{ matrix.node-version }} | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: ${{ matrix.node-version }} | ||
| cache: 'npm' | ||
| - run: npm ci | ||
| - run: npm run build --if-present | ||
| - run: npm test |
Comment on lines
+6
to
+10
| on: | ||
| push: | ||
| branches: [ "master" ] | ||
| pull_request: | ||
| branches: [ "master" ] |
bloodf
pushed a commit
to bloodf/durindoor
that referenced
this pull request
Jul 9, 2026
Source: decolua/9router#2474 Lock: origin/dev@a3c97f2a49910278081dfcf1c9d6f847d2da6d6d Hand-ported the upstream 'Add Node.js CI workflow' file onto the two-branch DurinDoor release model. Upstream triggers on master; this fork targets dev + main. npm ci replaced with npm install --no-audit --no-fund (no committed root lockfile; .gitignore:61), cache:npm dropped, build made unconditional, and the Node matrix narrowed to 20 to match ci.yml / test.yml. The upstream npm test step is omitted because DurinDoor already runs the vitest suite and no-regression gate in test.yml. Skips: duplicated test step to avoid red CI from inherited baseline drifts. NOTE: This workflow is intentionally a subset of the existing ci.yml; see PR body for why the upstream file is still preserved as a standalone port.
bloodf
pushed a commit
to bloodf/durindoor
that referenced
this pull request
Jul 9, 2026
Source: decolua/9router#2474 Lock: origin/dev@a3c97f2a49910278081dfcf1c9d6f847d2da6d6d Hand-ported the upstream 'Add Node.js CI workflow' file onto the two-branch DurinDoor release model. Upstream triggers on master; this fork targets dev + main. Keeps npm ci and cache:npm because package-lock.json is tracked in this fork (verified via git ls-files). Build made unconditional to avoid silently hiding regressions, and Node matrix narrowed to 20 to match ci.yml / test.yml. Upstream npm test step omitted because DurinDoor already runs the vitest suite and no-regression gate in test.yml. Fixes chatgpt-codex-connector review: use the committed lockfile (npm ci + cache:npm).
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
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.
This workflow sets up a CI pipeline for Node.js applications, including installation of dependencies, building the code, and running tests across multiple Node.js versions.