Add CI workflow for Chrome extension validation and repository setup#8
Merged
Conversation
daveshenal
commented
Jun 30, 2026
daveshenal
commented
Owner
- Adding a .gitignore file.
- Introducing a CI workflow to validate the Chrome extension.
- Skipping CI runs for documentation only PRs to reduce unnecessary workflow executions.
Initialize .gitignore with common patterns for Node.js projects, OS-specific files, build artifacts, and Chrome extension/certificate files.
Add GitHub Actions workflow to validate the extension on every push to main and pull request. The workflow checks for valid manifest.json, required files, JS syntax errors, and verifies manifest references match the filesystem.
Add paths-ignore to pull_request trigger to prevent CI workflows from running when only documentation or LICENSE files are modified. This reduces unnecessary build overhead for documentation only updates.
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
2 participants
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.