-
Notifications
You must be signed in to change notification settings - Fork 52
PSSA 1.21.0 docs changes from PSSA repo #99
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
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). |
Just saw the message around relative links. Will inspect the diff and revert those changes. Putting PR back into draft. |
…erent between PSSA vs MicrosoftDocs
This comment was marked as outdated.
This comment was marked as outdated.
reference/docs-conceptual/PSScriptAnalyzer/Rules/AvoidSemicolonsAsLineTerminators.md
Outdated
Show resolved
Hide resolved
…nsAsLineTerminators.md
This comment was marked as outdated.
This comment was marked as outdated.
@bergmeister Thanks for submitting the PR. I have marked it as |
Thanks @sdwheeler . Can you sync the change in your last commit back to PSSA please: https://github.com/PowerShell/PSScriptAnalyzer/blob/master/docs/Rules/AvoidSemicolonsAsLineTerminators.md |
Yes. |
Docs Build status updates of commit c99d53d: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
@sdwheeler PSSA has been released now: https://github.com/PowerShell/PSScriptAnalyzer/releases/tag/1.21.0 |
Learn Build status updates of commit 2cc973f: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
PR Summary
Copied over from PSSA repo after the most rcent PR 1835 there were changes from this repo were synced back. Please note that this version isn't released yet so you might want to wait with merging or publishing until then.
Related PRs
PR Checklist