docs
docs copied to clipboard
fix: improving style guide
Why:
Closes: #31686
What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR adds examples of how not to write content in GitHub's documentation to their style guide.
Check off the following:
-
[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
- For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the
datadirectory.
- For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the
-
[x] For content changes, I have completed the self-review checklist.
Automatically generated comment âšī¸
This comment is automatically generated and will be overwritten every time changes are committed to this branch.
The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.
Content directory changes
You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
| Source | Preview | Production | What Changed |
|---|---|---|---|
contributing/style-guide-and-content-model/style-guide.md |
fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8 |
fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8 |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server
Howdy, @CBID2 đ ! It looks like you've asked @ethanpalm for assistance on the related issue. I'll go ahead and leaves this PR for now while we wait for his input đ thank you for taking this on!
Howdy, @CBID2 đ ! It looks like you've asked @ethanpalm for assistance on the related issue. I'll go ahead and leaves this PR for now while we wait for his input đ thank you for taking this on!
Thanks @nguyenalex836. You can give feedback too! :) I'm open to your thoughts
Howdy, @CBID2 đ ! It looks like you've asked @ethanpalm for assistance on the related issue. I'll go ahead and leaves this PR for now while we wait for his input đ thank you for taking this on!
Thanks @nguyenalex836. You can give feedback too! :) I'm open to your thoughts
That's very kind of you! đ This isn't my area of expertise, and Ethan will be the superior resource - but I appreciate the kind words! đ
write and "Admin"
Hi @ethanpalm. I made the changes.
Thanks very much for contributing! Your pull request has been merged đ You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues :zap: