fix: add ability to set required extensions for certain commands #428
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
Some commands, like powershell, require the files it runs to end with a particular extension. This change sets up this requirement with the ability to add more later. Signed-off-by: Donnie Adams <[email protected]>
thedadams
force-pushed
the
required-extensions
branch
from
1a99d2a to
ef2850d
Compare
g-linville
reviewed
Jun 4, 2024
g-linville
approved these changes
Jun 4, 2024
njhale
approved these changes
Jun 4, 2024
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.
Some commands, like powershell, require the files it runs to end with a particular extension. This change sets up this requirement with the ability to add more later.