| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Joey Aiello (@joeyaiello) @eslesar can you take a look? |
Sorry, something went wrong.
|
sergei (@vors) Joey Aiello (@joeyaiello) I think we should have a style guide, in the docs repo, that should be linked to in this section. I think having one line about style seems somewhat random here. |
Sorry, something went wrong.
|
I think this is reasonable. @eslesar isn't the docs repo for PowerShell consumers? I believe the consensus was to keep developer docs in one place, next to the code, in this repo, and style guides definitely fall under developer docs. |
Sorry, something went wrong.
|
I don't know of any such consensus that was reached regarding developer docs in this repo. Either way, if there is going to be a style guide in this repo, that's fine, but this doc is pretty lean, and I don't think we should try to include style here. Just my opinion. |
Sorry, something went wrong.
|
Andy Jordan (@andschwa) @eslesar Yes, that's true that the docs that are supposed to exist in this repository are specifically for people who are contributing in some way to the PowerShell/PowerShell project. However, I think @eslesar's point is that, if the style guide for dev docs vs. user docs is the same, why not simply link between them? |
Sorry, something went wrong.
|
I agree with @eslesar, and we probably should borrow this line into PowerShell-Docs repo at some point. At the moment, almost all markdown in PowerShell-Docs violates this rule, so there is more work to put it there, then just copying. I'm going to merge this PR, because I encounter cases, when I need to refer people to this sentence. |
Sorry, something went wrong.
Add note about one sentance per line to CONTRIBUTING.md
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.