🚀 [Feature]: Add settings control of repository linter #218
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
…mic environment variables; remove obsolete PSModule configuration files.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request centralizes linter configuration management by moving environment variables from the workflow file to a YAML manifest and introducing dynamic loading capabilities. The change enables more flexible control of repository linter settings through configuration files rather than hard-coded workflow values.
Key changes:
- Added dynamic environment variable loading from YAML manifest using PowerShell
- Centralized linter configuration in PSModule.yml manifest file
- Removed legacy configuration files (PSModule.json and PSModule.psd1)
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/workflow.yml | Added PowerShell as default shell and dynamic environment loading step for linter configuration |
| tests/srcWithManifestTestRepo/.github/PSModule.yml | Added Linter.env section with environment variables for linter control |
| tests/srcWithManifestTestRepo/.github/PSModule.psd1 | Removed legacy PowerShell configuration file |
| tests/srcWithManifestTestRepo/.github/PSModule.json | Removed legacy JSON configuration file |
…set environment variables; update documentation accordingly.
…move skip option for Linter in PSModule configuration.
…Module configuration
…o boolean in PSModule configuration
…nvironment variable processing
…yle descriptions and labels based on change types
…tion instead - Update /specify, /plan, /tasks, and /implement prompts to detect fork mode via git remote -v - Remove all references to .fork-info.json configuration file - Simplify fork contribution workflow with automatic detection - Add comprehensive linter configuration documentation to README
- Add instruction to check ALL changes in the branch using git diff - Ensure Docs label is only applied when ALL changes are documentation - Clarify that mixed changes should be classified by code changes, not docs - Use git diff origin/main...HEAD to analyze complete branch changes
…ation steps in prompt documentation
…arsing and output formatting
…ys for improved processing
…proved linter configuration
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…larity and consistency
- Updated /pr prompt to use consistent ordered list structure - PR descriptions now follow: 1) summary paragraph, 2) issue links, 3) detailed sections - Added clear guidance for release note formatting - Included example structure to illustrate proper format Fixes #218
…arity and security
…nd improve settings loading in workflow
…n execution steps
… GitHub token directly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The workflow now provides fine-grained control over repository linting behavior through simple configuration options. You can disable the linter entirely or customize which validations run by configuring super-linter environment variables directly in your settings file, giving you full control over code quality checks without modifying workflow files.
Linter Configuration
Added two new settings to control repository linting behavior:
Linter.Skip: Completely disable repository linting when set totrueLinter.env: Configure super-linter environment variables to customize which validations runWhat you need to do: Add these settings to your
.github/PSModule.ymlfile as needed.Disable the linter completely
Customize specific validations
Advanced configuration
See the super-linter environment variables documentation for all available options.