-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
ConvertFrom-Json: Add -DateKind parameter #10737
Conversation
Learn Build status updates of commit 4b0e51c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
ExpectationsThanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it. To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details. The docs team begins to review your PR if you request them to or if your PR meets these conditions:
You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge. While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST). |
@jborean93 Thanks for the update. The change need to be made to the 7.5 content once we create it. I am closing this PR for now. When we have a 7.5 release I will reopen it and ask you to update the PR. |
Hi @sdwheeler I've rebased the PR and put the changes in the 7.5 directory now that they are there, can this PR be reopened please? |
@jborean93 Thanks for the reminder. I have been meaning to reopen this. |
This comment was marked as outdated.
This comment was marked as outdated.
94ca185
to
ef05a59
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Learn Build status updates of commit b1b6ff0: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
b1b6ff0
to
0f403c2
Compare
Thanks @sdwheeler for the fixes. The PR this is based on PowerShell/PowerShell#20925 has been merged. I've rebased this branch on the latest in |
Learn Build status updates of commit 0f403c2: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
0f403c2
to
b5b88c4
Compare
Learn Build status updates of commit b5b88c4: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Documents the -DateKind parameter that is part of the PR PowerShell/PowerShell#20925.
b5b88c4
to
f781270
Compare
Learn Build status updates of commit f781270: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PR Summary
Documents the -DateKind parameter that is part of the
This should not be merged until/if PowerShell/PowerShell#20925 is accepted. There was no
7.5
folder so I'm unsure if that needs to change or not.PR Checklist