🩹 [Patch]: Update linting and git configuration and license year #308
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.
Description
This pull request includes several changes across different configuration files to update linters, modify validation settings, and update documentation. The most important changes are summarized below:
Linter Configuration Updates:
.github/linters/.jscpd.json
: Added a new configuration file forjscpd
with a threshold of 0, console reporting, and ignoring test files..github/linters/.powershell-psscriptanalyzer.psd1
: Updated thePSScriptAnalyzer
settings to enable various rules, including alignment, long lines, semicolon usage, brace placement, comment help, consistent indentation, and whitespace.Validation Settings:
.github/workflows/Linter.yml
: Changed validation settings by disablingVALIDATE_JSON_PRETTIER
and removingVALIDATE_GITLEAKS
andVALIDATE_POWERSHELL
.Documentation Updates:
Coverage.md
: Updated function coverage numbers and added new API endpoint coverage details. [1] [2] [3]LICENSE
: Updated the copyright year from 2024 to 2025.Minor Fixes:
.github/linters/.markdown-lint.yml
: Corrected the punctuation list format for theMD026
rule.Type of change
Checklist