-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document exit codes for dsc
#178
Labels
Issue-Documentation
Improvements or additions to documentation
Comments
michaeltlombardi
added a commit
to michaeltlombardi/DSC
that referenced
this issue
Aug 30, 2023
Prior to this change, the documentation for the `dsc` command did not include the exit codes that it may return. This change adds a section to the documentation that lists the exit codes and their meanings. This information is particularly important to integrating tools, like winget, that need to know the semantic meaning of the exit codes when calling `dsc`. - Resolves PowerShell#178
michaeltlombardi
added a commit
to michaeltlombardi/DSC
that referenced
this issue
Aug 31, 2023
Prior to this change, the documentation for the `dsc` command did not include the exit codes that it may return. This change adds a section to the documentation that lists the exit codes and their meanings. This information is particularly important to integrating tools, like winget, that need to know the semantic meaning of the exit codes when calling `dsc`. - Resolves PowerShell#178
SteveL-MSFT
added a commit
to michaeltlombardi/DSC
that referenced
this issue
Sep 1, 2023
SteveL-MSFT
added a commit
that referenced
this issue
Sep 1, 2023
(GH-178) Document `dsc` exit codes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary of the new feature / enhancement
Currently, there's no documentation for the exit codes that
dsc
returns, even though they have semantic meaning:DSC/dsc/src/util.rs
Lines 29 to 34 in 5a1f8b5
These exit codes should be documented in the root command document.
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: