diff --git a/.github/.copilot-codeGeneration-instructions.md b/.github/.copilot-codeGeneration-instructions.md deleted file mode 100644 index 9968ee8..0000000 --- a/.github/.copilot-codeGeneration-instructions.md +++ /dev/null @@ -1,14 +0,0 @@ -# Code Generation - -50-75 >= lines we need to modularize and separate concerns better. - -- Prefer modular, single-responsibility functions for maintainability. -- Separate concerns: avoid large, monolithic files or classes. -- Use clear, explicit types and interfaces for all public APIs. -- Avoid `any`; use strict TypeScript typing throughout. -- Follow project linting and formatting rules at all times. -- Use named exports/imports; avoid default exports for clarity. -- Write tests for all new code and edge cases. -- Document all exported functions and modules. -- Use async/await for asynchronous code, never callbacks. -- Optimize for readability and maintainability over cleverness. diff --git a/.github/.copilot-commit-message-instructions.md b/.github/.copilot-commit-message-instructions.md deleted file mode 100644 index 96a5538..0000000 --- a/.github/.copilot-commit-message-instructions.md +++ /dev/null @@ -1,53 +0,0 @@ -# Commit Messages - -Explain with detail what all has changed. - -We love emojis ๐Ÿš‚๐ŸŽ›๏ธ๐Ÿงถโฎ๏ธ๐Ÿ“ฆ๐Ÿ˜‚๐Ÿ˜Ž - -We use emojis in commit messages to make them more expressive and engaging. Hereโ€™s how we use them: - -x=major, y=minor, z=patch - -examples: - -``` -๐Ÿš€ Use ๐Ÿ‘ emojis, there are many to choose from, conventional commit message format. ex. (): -``` - -```text -๐ŸŒŸ FEAT: We want a good release. x.Y.z ... -``` - -or - -```text -๐Ÿ› FIX: We fixed a bug in the code. x.y.Z ... -``` - -or - -```text -๐Ÿงน CHORE: We cleaned up the codebase. x.y.z ... -``` - -or - -```text -๐Ÿšจ BREAKING CHANGE: We made a change that breaks backward compatibility. X.y.z ... -``` - -## Commit Message Guidelines - -We use semantic-release syntax for messaging. - -- ๐Ÿ˜„ Emojis add clarity and fun to commit messages. -- ๐Ÿท๏ธ They help visually categorize the type of change. -- ๐Ÿ‘€ Emojis make scanning commit history faster and more engaging. -- ๐Ÿค They foster a positive, expressive team culture. -- โšก๏ธ Emojis can highlight breaking changes or important updates. -- ๐Ÿ“š They make our project history more memorable and welcoming. - -- chore: (for changes that do not modify the public API, will not trigger a release) -- fix: (for bug fixes, triggers a patch release) -- feat: (for new features, triggers a minor release) -- BREAKING CHANGE: (in the body or footer, triggers a major release) diff --git a/.github/.copilot-pull-request-description-instructions.md b/.github/.copilot-pull-request-description-instructions.md deleted file mode 100644 index e69de29..0000000 diff --git a/.github/.copilot-test-instructions.md b/.github/.copilot-test-instructions.md deleted file mode 100644 index 25b4368..0000000 --- a/.github/.copilot-test-instructions.md +++ /dev/null @@ -1,9 +0,0 @@ - -# Test Setup - -We test using vitest, and typically the `--watch` flag is used to keep the test runner active for continuous feedback during development. Even if the VS Code Vitest extension is installed, we prefer to test using the command line to ensure consistency across environments. - -```bash -yarn vitest --watch - -``` diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md deleted file mode 100644 index 7cde346..0000000 --- a/.github/copilot-instructions.md +++ /dev/null @@ -1,22 +0,0 @@ -# Copilot Instructions - -1. Use Copilot for suggestions, not final code. -2. Review all output for correctness and security. -3. Never accept hardcoded secrets or credentials. -4. Prefer clear, explicit, and idiomatic code. -5. Follow project linting and TypeScript rules strictly. -6. Use strict types; avoid `any` unless unavoidable. -7. Do not disable type checks or linting. -8. Use named exports/imports; avoid default exports. -9. Write tests for all new code. -10. Document all public APIs. -11. Use functional patterns and avoid side effects. -12. Use async/await for async code. -13. Handle errors explicitly. -14. Never mutate input arguments. -15. Use ES modules syntax. -16. Keep functions small and focused. -17. Use destructuring where helpful. -18. Do not copy code from external sources without attribution. -19. Avoid cleverness; optimize for maintainability. -20. All code must be reviewed before acceptance. diff --git a/.github/instructions/general-coding.instructions.md b/.github/instructions/general-coding.instructions.md deleted file mode 100644 index e69de29..0000000 diff --git a/.github/instructions/typescript-react.instructions.md b/.github/instructions/typescript-react.instructions.md deleted file mode 100644 index e69de29..0000000 diff --git a/CHANGELOG.md b/CHANGELOG.md index 4c3d7eb..88ec4e8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,5 @@ +## [1.0.4](https://github.com/variablesoftware/github-actions-node-setup-and-test/compare/v1.0.3...v1.0.4) (2025-06-20) + ## [1.0.3](https://github.com/variablesoftware/github-actions-node-setup-and-test/compare/v1.0.2...v1.0.3) (2025-06-09) ## [1.0.2](https://github.com/variablesoftware/github-actions-node-setup-and-test/compare/v1.0.1...v1.0.2) (2025-06-06) diff --git a/package.json b/package.json index 14e7f02..8ce58fd 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "github-actions-node-setup-and-test", - "version": "1.0.3", + "version": "1.0.4", "description": "Reusable composite GitHub Action for setup and test steps.", "main": "action.yml", "license": "MIT",