actions/javascript-action
1
0
Fork 0
mirror of https://github.com/actions/javascript-action.git synced 2025-12-10 12:52:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix linting errors

Browse Source
This commit is contained in:
Nick Alteen
2025-07-11 13:44:09 -04:00
parent d60fcf10bb
commit 4a38b08003
3 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.github/copilot-instructions.md vendored
View File

@@ -18,8 +18,8 @@ code it is generated from.
| `.devcontainer/` | Development Container Configuration | | `.devcontainer/` | Development Container Configuration |
| `.github/` | GitHub Configuration | | `.github/` | GitHub Configuration |
| `.licenses/` | License Information | | `.licenses/` | License Information |
| `.vscode/` | VSCode Configuration | | `.vscode/` | Visual Studio Code Configuration |
| `badges/` | Badges for README | | `badges/` | Badges for readme |
| `dist/` | Generated JavaScript Code | | `dist/` | Generated JavaScript Code |
| `src/` | JavaScript Source Code | | `src/` | JavaScript Source Code |
| `.env.example` | Environment Variables Example for `@github/local-action` | | `.env.example` | Environment Variables Example for `@github/local-action` |

4
.github/prompts/create-release-notes.prompt.md vendored
View File

@@ -16,7 +16,7 @@ Ensure you adhere to the following guidelines when creating release notes:
- Use a clear and consistent format for the release notes - Use a clear and consistent format for the release notes
- Include a summary of the changes made in the release - Include a summary of the changes made in the release
- Highlight any new features, improvements, or bug fixes - Highlight any new features, improvements, or bugfixes
- If applicable, include instructions for upgrading or migrating to the new - If applicable, include instructions for upgrading or migrating to the new
version version
- Use technical language that is appropriate for the audience, but avoid jargon - Use technical language that is appropriate for the audience, but avoid jargon
@@ -37,4 +37,4 @@ nature of the changes, please make sure to adjust the release notes accordingly:
- For **major** changes, include a detailed description of the breaking changes - For **major** changes, include a detailed description of the breaking changes
and how users can adapt to them and how users can adapt to them
- For **minor** changes, highlight new features and improvements - For **minor** changes, highlight new features and improvements
- For **patch** changes, focus on bug fixes and minor improvements - For **patch** changes, focus on bugfixes and minor improvements