Ci workflows - #14
Merged
Merged
Conversation
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.
This pull request introduces new development guidelines and strengthens pre-commit checks to improve code quality and consistency. The main changes include adding comprehensive Copilot instructions for commit messages, code quality, and testing, as well as updating the pre-commit hook to enforce formatting and unit testing before commits.
Development guidelines:
.github/copilot-instructions.mdfile detailing conventions for commit messages (using Conventional Commits, focusing on user benefits), code quality standards (required verification commands, recommended VS Code tasks), and testing practices (unit and integration test locations, coverage requirements, and best practices for mocks and validation).Pre-commit enforcement:
.husky/pre-committo require both formatting checks (npm run format:check) and unit tests (npm run test:unit) in addition to linting before allowing a commit, ensuring higher code quality and fewer regressions.