10BC0 Documentation Cleanup by RDIL · Pull Request #8851 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]

Skip to content

Documentation Cleanup#8851

Merged
TravisEz13 merged 18 commits intoPowerShell:masterfrom
RDIL:patch-5
Mar 5, 2019
Merged

Documentation Cleanup#8851
TravisEz13 merged 18 commits intoPowerShell:masterfrom
RDIL:patch-5

Conversation

@RDIL
Copy link
Contributor
@RDIL RDIL commented Feb 9, 2019

PR Summary

  • Fixed MDLint Issues
  • Fixed Grammar Issues
  • Added/fixed links

Also sorry I had to reuse an old patch branch meaning one of Dongbo's commits is still there

PR Context

Improves parts of documentation.

PR Checklist

When building for multiple architectures, be sure to use the `-clean` switch as cmake will cache the previous run and the wrong compiler will be used to generate the subsequent architectures.

After that, the binary `pwrshplugin.dll`, its PDB file, and `powershell.core.instrumentation.dll` will be placed under 'src\powershell-win-core'.
After that, the binary `pwrshplugin.dll`, its PDB file, and `powershell.core.instrumentation.dll` will be placed under `src\powershell-win-core`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Native Components - we need to update the section - native components is not in the repo. Perhaps @adityapatwardhan and @PaulHigin could help.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps so.

@iSazonov iSazonov added the CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log label Feb 9, 2019
Below is a summary of our approach to handing breaking changes including what kinds of things constitute breaking changes, how we categorize them, and how we decide what we're willing to take.

Note that these rules only apply to existing stable features that have shipped in a supported release. New features marked as “in preview” that are still under development may be modified from one preview release to the next. These are not considered breaking changes.
Note that these rules only apply to existing stable features that have shipped in a supported release. New features marked as “in preview” that are still under development may be modified from one preview release to the next.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps we should change "in preview" to experimental now that we have that feature

@SteveL-MSFT

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed

TravisEz13 and others added 4 commits February 9, 2019 15:42
Co-Authored-By: RDIL <jumbocakefdx@gmail.com>
Co-Authored-By: RDIL <jumbocakefdx@gmail.com>
Co-Authored-By: RDIL <jumbocakefdx@gmail.com>
Co-Authored-By: RDIL <jumbocakefdx@gmail.com>
@RDIL
Copy link
Contributor Author
RDIL commented Feb 11, 2019

@sdwheeler please update your review

@iSazonov
Copy link
Collaborator
iSazonov commented Mar 1, 2019

@TravisEz13 Could you merge?

@RDIL
Copy link
Contributor Author
RDIL commented Mar 5, 2019

Commenting to make sure stale bot doesn't tag the PR.
@TravisEz13 this should be ready for merge.

@TravisEz13 TravisEz13 merged commit 7cc4889 into PowerShell:master Mar 5, 2019
@RDIL RDIL deleted the patch-5 branch March 5, 2019 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

0