Repository navigation
ci: test and build the beacon on every pull request - #8
Merged
Merged
Conversation
Contributor
Author
|
@IvanChepurnyi I stacked #8 on #7, so it shows that commit too until #7 merges; after that the diff is only ci.yml. |
Member
|
Can you rebase, please? |
Runs the Vitest suite and the build, and fails when the committed beacon.js does not match what its source builds.
Contributor
Author
|
Updated the PR! |
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.
Runs the Vitest suite and the build on every pull request and push to main, then fails if the committed beacon.js differs from what its source builds. The identifier bug in #7 lived in that committed bundle, so this catches the two drifting apart. Read-only permissions, actions pinned by commit SHA, install scripts off.