test: verify pr-review workflow - #1
Merged
Merged
Conversation
There was a problem hiding this comment.
Low-risk PR that modifies the CI workflow to build pi-relay from source instead of installing it globally via npm, and adds an "automation" keyword to package.json. The workflow changes are logically sound: cloning with --depth=1, running npm ci and npm run build, and correctly propagating the root path via GITHUB_OUTPUT. Secret handling remains unchanged and proper. No security, correctness, or breaking-change concerns.
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.
Testing the PR review CI workflow. This is a trivial change (added a keyword to package.json) to trigger the workflow and verify it runs end-to-end.