mirror of https://github.com/nginx/nginx
- Issue templates are replaced with forms. Forms allow to explicitly ask for certain info before an issue is opened, they can be programmatically queried via GH actions to get the data in fields. - Added language around GH discussions vs the forum in the issue forms. - Added GH discussions templates. These templates delineate which types of discussions belong on GitHub vs the community forum. - Created SUPPORT.md to delineate which types of topics belong on GitHub vs different support channels (community forum/docs/commercial support). - Updated CONTRIBUTING.md: - Removed text that belongs in SUPPORT.md. - Added F5 CLA clarifying text. - Added badges to README.md. Most of these are there to make information even clearer, moreso for users reading README.md from sources outside GitHub.pull/1016/head
parent
ab4f5b2d32
commit
367113670e
@ -0,0 +1,15 @@ |
||||
--- |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
For NGINX troubleshooting/technical help, please visit our community forum instead of asking your questions here. We will politely redirect these types of questions to the forum. |
||||
- type: textarea |
||||
id: general |
||||
attributes: |
||||
label: What would you like to discuss? |
||||
description: Please provide as much context as possible. Remember that only general discussions related to the NGINX codebase will be addressed on GitHub. For anything else, please visit our [community forum](https://community.nginx.org/). |
||||
value: | |
||||
I would like to discuss... |
||||
validations: |
||||
required: true |
||||
@ -0,0 +1,15 @@ |
||||
--- |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
For NGINX troubleshooting/technical help, please visit our community forum instead of asking your questions here. We will politely redirect these types of questions to the forum. |
||||
- type: textarea |
||||
id: ideas |
||||
attributes: |
||||
label: What idea would you like to discuss? |
||||
description: Please provide as much context as possible. Remember that only ideas related to the NGINX codebase will be addressed on GitHub. For anything else, please visit our [community forum](https://community.nginx.org/). |
||||
value: | |
||||
I have an idea for... |
||||
validations: |
||||
required: true |
||||
@ -0,0 +1,15 @@ |
||||
--- |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
For NGINX troubleshooting/technical help, please visit our community forum instead of asking your questions here. We will politely redirect these types of questions to the forum. |
||||
- type: textarea |
||||
id: q-a |
||||
attributes: |
||||
label: What question do you have? |
||||
description: Please provide as much context as possible. Remember that only questions related to the NGINX codebase will be addressed on GitHub. For anything else, please visit our [community forum](https://community.nginx.org/). |
||||
value: | |
||||
I would like to know... |
||||
validations: |
||||
required: true |
||||
@ -1,38 +0,0 @@ |
||||
--- |
||||
name: Bug report |
||||
about: Create a report to help us improve |
||||
title: "" |
||||
labels: "bug" |
||||
--- |
||||
|
||||
### Environment |
||||
|
||||
Include the result of the following commands: |
||||
- `nginx -V` |
||||
- `uname -a` |
||||
|
||||
### Description |
||||
|
||||
Describe the bug in full detail including expected and actual behavior. |
||||
Specify conditions that caused it. Provide the relevant part of nginx |
||||
configuration and debug log. |
||||
|
||||
- [ ] The bug is reproducible with the latest version of nginx |
||||
- [ ] The nginx configuration is minimized to the smallest possible |
||||
to reproduce the issue and doesn't contain third-party modules |
||||
|
||||
#### nginx configuration |
||||
|
||||
``` |
||||
# Your nginx configuration here |
||||
``` |
||||
or share the configuration in [gist](https://gist.github.com/). |
||||
|
||||
#### nginx debug log |
||||
|
||||
It is advised to enable |
||||
[debug logging](http://nginx.org/en/docs/debugging_log.html). |
||||
``` |
||||
# Your nginx debug log here |
||||
``` |
||||
or share the debug log in [gist](https://gist.github.com/). |
||||
@ -0,0 +1,106 @@ |
||||
--- |
||||
name: 🐛 Bug report |
||||
description: Create a report to help us improve |
||||
labels: bug |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
Thanks for taking the time to fill out this bug report! |
||||
|
||||
Before you continue filling out this report, please take a moment to check that your bug has not been [already reported on GitHub][issue search], is reproducible with the latest version of nginx, and does not involve any third-party modules 🙌 |
||||
|
||||
Remember to redact any sensitive information such as authentication credentials and/or license keys! |
||||
|
||||
**Note:** If you are seeking community support, please start a new topic in the [NGINX Community forum][forum]. If you wish to discuss the codebase, please start a new thread via [GitHub discussions][discussions]. |
||||
|
||||
[issue search]: https://github.com/nginx/nginx/search?q=is%3Aissue&type=issues |
||||
[discussions]: https://github.com/nginx/nginx/discussions |
||||
[forum]: https://community.nginx.org |
||||
|
||||
- type: textarea |
||||
id: overview |
||||
attributes: |
||||
label: Bug Overview |
||||
description: A clear and concise overview of the bug. |
||||
placeholder: When I do "X", "Y" happens instead of "Z". |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: behavior |
||||
attributes: |
||||
label: Expected Behavior |
||||
description: A clear and concise description of what you expected to happen. |
||||
placeholder: When I do "X", I expect "Z" to happen. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: steps |
||||
attributes: |
||||
label: Steps to Reproduce the Bug |
||||
description: Detail the series of steps required to reproduce the bug. |
||||
placeholder: When I run "X" using [...], "X" fails with "Y" error message. If I check the terminal outputs and/or logs, I see the following info. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: configuration |
||||
attributes: |
||||
label: NGINX Configuration |
||||
description: Please provide your NGINX configuration. Minimize it to the smallest possible configuration that reproduces the issue. |
||||
value: | |
||||
``` |
||||
# Your NGINX configuration |
||||
``` |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: environment |
||||
attributes: |
||||
label: NGINX version and build configuration options |
||||
description: Please provide details about your NGINX build. |
||||
value: | |
||||
The output of `nginx -V`: [...] |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: environment |
||||
attributes: |
||||
label: Environment where NGINX is being built and/or deployed |
||||
description: Please provide details about your environment. |
||||
value: | |
||||
- Target deployment platform: [e.g. AWS/GCP/local cluster/etc...] |
||||
- Target OS: [e.g. RHEL 9/Ubuntu 24.04/etc...] |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: environment |
||||
attributes: |
||||
label: Architecture where NGINX is being built and/or deployed |
||||
description: Please provide details about your deployment environment. |
||||
value: | |
||||
The output of `uname -a`: [...] |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: logs |
||||
attributes: |
||||
label: NGINX Debug Log |
||||
description: Please provide your NGINX debug log. See this [doc](http://nginx.org/en/docs/debugging_log.html) for details on how to enable it. |
||||
value: | |
||||
``` |
||||
# Your NGINX debug log |
||||
``` |
||||
|
||||
- type: textarea |
||||
id: context |
||||
attributes: |
||||
label: Additional Context |
||||
description: Add any other context about the problem here. |
||||
placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this issue in here. |
||||
@ -0,0 +1,12 @@ |
||||
--- |
||||
blank_issues_enabled: false |
||||
contact_links: |
||||
- name: 💬 Talk to the NGINX community! |
||||
url: https://community.nginx.org |
||||
about: A community forum for NGINX users, developers, and contributors |
||||
- name: 📝 Code of Conduct |
||||
url: https://www.contributor-covenant.org/version/2/1/code_of_conduct |
||||
about: NGINX follows the Contributor Covenant Code of Conduct to ensure a safe and inclusive community |
||||
- name: 💼 For commercial & enterprise users |
||||
url: https://www.f5.com/products/nginx |
||||
about: F5 offers a wide range of NGINX products for commercial & enterprise users |
||||
@ -1,18 +0,0 @@ |
||||
--- |
||||
name: Feature request |
||||
about: Suggest a feature for nginx |
||||
title: "" |
||||
labels: "feature" |
||||
--- |
||||
|
||||
### Describe the feature you'd like to add to nginx |
||||
|
||||
A clear and concise description of the feature. |
||||
|
||||
### Describe the problem this feature solves |
||||
|
||||
A clear and concise description of the problem. |
||||
|
||||
### Additional context |
||||
|
||||
Add any other context about the feature request here. |
||||
@ -0,0 +1,40 @@ |
||||
--- |
||||
name: ✨ Feature request |
||||
description: Suggest an idea for this project |
||||
labels: enhancement |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
Thanks for taking the time to fill out this feature request! |
||||
|
||||
Before you continue filling out this request, please take a moment to check that your feature has not been [already requested on GitHub][issue search] 🙌 |
||||
|
||||
**Note:** If you are seeking community support, please start a new topic in the [NGINX Community forum][forum]. If you wish to discuss the codebase, please start a new thread via [GitHub discussions][discussions]. |
||||
|
||||
[issue search]: https://github.com/nginx/nginx/search?q=is%3Aissue&type=issues |
||||
[discussions]: https://github.com/nginx/nginx/discussions |
||||
[forum]: https://community.nginx.org |
||||
|
||||
- type: textarea |
||||
id: overview |
||||
attributes: |
||||
label: Feature Overview |
||||
description: A clear and concise description of what the feature request is. |
||||
placeholder: I would like this project to be able to do "X". |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: alternatives |
||||
attributes: |
||||
label: Alternatives Considered |
||||
description: Detail any potential alternative solutions/workarounds you've used or considered. |
||||
placeholder: I have done/might be able to do "X" in this project by doing "Y". |
||||
|
||||
- type: textarea |
||||
id: context |
||||
attributes: |
||||
label: Additional Context |
||||
description: Add any other context about the problem here. |
||||
placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this feature request here. |
||||
@ -1,10 +1,10 @@ |
||||
### Proposed changes |
||||
|
||||
Describe the use case and detail of the change. |
||||
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue using one of the [supported keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in this PR's description or commit message. |
||||
|
||||
If this pull request addresses an issue on GitHub, make sure to reference that |
||||
issue using one of the |
||||
[supported keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue). |
||||
### Checklist |
||||
|
||||
Before creating a pull request, make sure to comply with the |
||||
[Contributing Guidelines](https://github.com/nginx/nginx/blob/master/CONTRIBUTING.md). |
||||
Before creating a PR, run through this checklist and mark each as complete: |
||||
|
||||
- [ ] I have read the [contributing guidelines](/CONTRIBUTING.md). |
||||
- [ ] I have checked that NGINX compiles and runs after adding my changes. |
||||
|
||||
@ -0,0 +1,48 @@ |
||||
# Support |
||||
|
||||
## Ask a Question |
||||
|
||||
We use GitHub issues for tracking bugs and feature requests |
||||
related to this project. |
||||
|
||||
If you don't know how something in the codebase works, are curious if NGINX |
||||
is capable of achieving your desired functionality or want to discuss the |
||||
implementation of an existing or in development feature, please start a |
||||
GitHub discussion! |
||||
|
||||
## NGINX Specific Questions and/or Issues |
||||
|
||||
This project isn't the right place to get support for NGINX and/or NGINX |
||||
troubleshooting questions, but the following resources are available below. |
||||
Thanks for your understanding! |
||||
|
||||
### Community Forum |
||||
|
||||
We have a [community forum](https://community.nginx.org/)! |
||||
If you have any NGINX specific questions and/or issues, |
||||
try checking out the [`NGINX category`](https://community.nginx.org/c/projects/nginx/23). |
||||
For general discussions around anything tangentially NGINX related, |
||||
check out the [`General Discussion category`](https://community.nginx.org/c/general-discussion/34). |
||||
Both fellow community members and NGINXers might be able to help you! :) |
||||
|
||||
### Documentation |
||||
|
||||
For a comprehensive list of all NGINX directives, check out <https://nginx.org>. |
||||
|
||||
For a comprehensive list of administration and deployment guides for all |
||||
NGINX products, check out <https://docs.nginx.com>. |
||||
|
||||
## Contributing |
||||
|
||||
Please see the [contributing guide](/CONTRIBUTING.md) for guidelines |
||||
on how to best contribute to this project. |
||||
|
||||
## Commercial Support |
||||
|
||||
Commercial support for this project is available. |
||||
Please get in touch with [F5 sales](https://www.f5.com/products/get-f5/) |
||||
or check your contract details for more information! |
||||
|
||||
## Community Support |
||||
|
||||
Community support is offered on a best effort basis through any of our active communities. |
||||
Loading…
Reference in new issue