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
Help us keep this project open and inclusive. Please read and follow our [Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
22
23
23
24
## <aname="issue"></a> Found an Issue?
25
+
24
26
If you find a bug in the source code or a mistake in the documentation, you can help us by
25
27
[submitting an issue](#submit-issue) to the GitHub Repository. Even better, you can
26
28
[submit a Pull Request](#submit-pr) with a fix.
27
29
28
30
## <aname="feature"></a> Want a Feature?
29
-
You can *request* a new feature by [submitting an issue](#submit-issue) to the GitHub
30
-
Repository. If you would like to *implement* a new feature, please submit an issue with
31
+
32
+
You can _request_ a new feature by [submitting an issue](#submit-issue) to the GitHub
33
+
Repository. If you would like to _implement_ a new feature, please submit an issue with
31
34
a proposal for your work first, to be sure that we can use it.
32
35
33
-
***Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
36
+
-**Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
34
37
35
38
## <aname="submit"></a> Submission Guidelines
36
39
37
40
### <aname="submit-issue"></a> Submitting an Issue
41
+
38
42
Before you submit an issue, search the archive, maybe your question was already answered.
39
43
40
44
If your issue appears to be a bug, and hasn't been reported, open a new issue.
41
45
Help us to maximize the effort we can spend fixing issues and adding new
42
-
features, by not reporting duplicate issues. Providing the following information will increase the
46
+
features, by not reporting duplicate issues. Providing the following information will increase the
43
47
chances of your issue being dealt with quickly:
44
48
45
-
***Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
46
-
***Version** - what version is affected (e.g. 0.1.2)
47
-
***Motivation for or Use Case** - explain what are you trying to do and why the current behavior is a bug for you
48
-
***Browsers and Operating System** - is this a problem with all browsers?
49
-
***Reproduce the Error** - provide a live example or a unambiguous set of steps
50
-
***Related Issues** - has a similar issue been reported before?
51
-
***Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
49
+
-**Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
50
+
-**Version** - what version is affected (e.g. 0.1.2)
51
+
-**Motivation for or Use Case** - explain what are you trying to do and why the current behavior is a bug for you
52
+
-**Browsers and Operating System** - is this a problem with all browsers?
53
+
-**Reproduce the Error** - provide a live example or a unambiguous set of steps
54
+
-**Related Issues** - has a similar issue been reported before?
55
+
-**Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
52
56
causing the problem (line of code or commit)
53
57
54
58
You can file new issues by providing the above information at the corresponding repository's issues link: https://github.com/[organization-name]/[repository-name]/issues/new].
55
59
56
60
### <aname="submit-pr"></a> Submitting a Pull Request (PR)
61
+
57
62
Before you submit your Pull Request (PR) consider the following guidelines:
58
63
59
-
* Search the repository (https://github.com/[organization-name]/[repository-name]/pulls) for an open or closed PR
64
+
- Search the repository (https://github.com/[organization-name]/[repository-name]/pulls) for an open or closed PR
60
65
that relates to your submission. You don't want to duplicate effort.
61
66
62
-
* Make your changes in a new git fork:
67
+
- Make your changes in a new git fork:
68
+
69
+
- Commit your changes using a descriptive commit message
70
+
- Push your fork to GitHub:
71
+
- In GitHub, create a pull request
72
+
- If we suggest changes then:
63
73
64
-
* Commit your changes using a descriptive commit message
65
-
* Push your fork to GitHub:
66
-
* In GitHub, create a pull request
67
-
* If we suggest changes then:
68
-
* Make the required updates.
69
-
* Rebase your fork and force push to your GitHub repository (this will update your Pull Request):
74
+
- Make the required updates.
75
+
- Rebase your fork and force push to your GitHub repository (this will update your Pull Request):
This sample shows how to build a serverless ChatGPT-like with Retrieval-Augmented Generation AI application using [Azure Static Web Apps](https://learn.microsoft.com/azure/static-web-apps/overview), [Azure Functions](https://learn.microsoft.com/azure/azure-functions/functions-overview?pivots=programming-language-javascript) and the [LangChain.js library](https://js.langchain.com/). This can be used as a starting point for building more complex AI applications.
0 commit comments