PS: Open source the powershell extractor #81
Merged
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
MathiasVP
force-pushed
the
open-source-powershell-extractor
branch
from
bb28f12 to
95d02e6
Compare
dilanbhalla
approved these changes
Aug 23, 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.
This PR moves the powershell extractor and the related script files to the public repo. Once this PR has gone in we can properly start on the QL work for powershell support.
I haven't made any changes to the extractor code itself. I have however done the following:
README.mdto reflect the above changes.@dilanbhalla I noticed that the original README file had a line that said:
which I've totally ignored (🙈) since I don't know anything about this NuGet package creation. Do you know if I've broken anything by this restructuring (and how I can test this)?