Added my contribution to get-code-suggestions.md
Updated the documentation with additional information and made minor improvements. This is my contribution as part of the GitHub documentation project.
Why:
Closes:
-->
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
- [x] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR.
- [x] The changes in this PR meet the docs fundamentals that are required for all content.
- [x] All CI checks are passing and the changes look good in the review environment.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
How to review these changes 👓
Thank you for your contribution. To review these changes, choose one of the following options:
A Hubber will need to deploy your changes internally to review.
Table of review links
Note: Please update the URL for your staging server or codespace.
The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.
| Source | Review | Production | What Changed |
|---|---|---|---|
copilot/how-tos/get-code-suggestions/get-code-suggestions.md |
fpt ghec |
fpt ghec |
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
🤖 This comment is automatically generated.
@Nasiquejahangr Thanks for opening a PR! It's possible this should have been an issue first, because even though this looks like good information, I'm not completely sure this is the article where we would want it, and the section will definitely need to go somewhere else even if it is, because the "Further reading" section should always be the last one. I need to check in with the rest of the team about this, and I'll get back to you.
Fff