Add GitHub best practices infrastructure#7
Merged
Conversation
CI runs lint and tests on push/PR to master using Node 20. Dependabot checks npm dependencies weekly and GitHub Actions monthly.
- SECURITY.md with supported versions and reporting instructions - PR template with summary and test plan checklist - Bug report template alongside existing AI content report template
The project convention is to keep commit messages clean without AI-generated annotations.
The vitest/config import works correctly but the eslint import resolver cannot locate it. Suppress the false positive so CI lint passes cleanly.
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
.github/workflows/ci.yml): Runs lint + tests on push/PR to master (Node 20, ubuntu-latest).github/dependabot.yml): Weekly npm updates (grouped by prod/dev), monthly GitHub Actions updatesSECURITY.md): Supported versions, private vulnerability reporting instructionsPost-merge follow-up
After merging, configure repo settings via
gh:master(require CI status checks, require PR)Test Plan