You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 10-Challenging-GitHub-Copilot-with-SQL/README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ In this workshop, you will:
26
26
- Use advanced GitHub Copilot interaction techniques to deal with complex problems regarding SQL queries.
27
27
- Iterate, validate, and refine answers to get better and more accurate suggestions
28
28
- Apply generic concepts that can improve suggestions and select from different strategies that can yield better results.
29
-
- Get a clear understanding on poor prompting techniques, and how these can
29
+
- Get a clear understanding of poor prompting techniques, and how these can
30
30
affect drastically the output from GitHub Copilot.
31
31
32
32
## :mega: Prerequisites
@@ -102,7 +102,7 @@ In SQL, this could involve ensuring that empty datasets, null values, or unexpec
102
102
> Thinking through edge cases helps you build more resilient, generalized solutions.
103
103
104
104
### 8. Use Tools Effectively
105
-
Whether you’re using GitHub Copilot, a query builder, or another form of automation, leverage the tools at your disposal but make sure you're guiding them with the right context. Tools are great for speeding up the generation, but they still need well-structured inputs and validation from you.
105
+
Whether you’re using GitHub Copilot, a query builder, or another form of automation, leverage the tools at your disposal, but make sure you're guiding them with the right context. Tools are great for speeding up the generation, but they still need well-structured inputs and validation from you.
106
106
107
107
For Copilot, ensure that your prompts are detailed, but concise. Tools often work best when given structured input that leaves little ambiguity.
108
108
@@ -146,7 +146,7 @@ Although not required, some of the features this workshop covers are in these Mi
146
146
147
147
## Contributing
148
148
149
-
This project welcomes contributions and suggestions. Most contributions require you to agree to a
149
+
This project welcomes contributions and suggestions. Most contributions require you to agree to a
150
150
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
151
151
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
152
152
@@ -155,7 +155,7 @@ a CLA and decorate the PR appropriately (e.g., status check, comment). Simply fo
155
155
provided by the bot. You will only need to do this once across all repos using our CLA.
156
156
157
157
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
158
-
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
158
+
For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
159
159
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
160
160
161
161
## Trademarks
@@ -164,4 +164,4 @@ This project may contain trademarks or logos for projects, products, or services
0 commit comments