💡 How to submit an issue

Hi folks,

The GitHub issues list is an integral part of our community. We use it to track bugs, feature requests, and other things. Please follow the guidelines below to make sure your issue is handled correctly.

### 📔 Before you submit an issue

1. Make sure you are using the latest version of Answer.
2. Search the [issue tracker](https://github.com/apache/incubator-answer/issues) to make sure your issue hasn't been reported before.

### 🌐 English only

Please use English to describe your issue. We can communicate in other languages, but the issue list is only in English.

### ✏️ How to write a good issue

1. Provide a clear and descriptive title.
2. Describe the steps to reproduce the issue. Provide as much detail as possible.
3. Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use [Markdown code blocks](https://help.github.com/articles/markdown-basics/#multiple-lines).
4. Respond to questions or requests for additional information by the time limit. If we need more information but don't hear from you, we may close the issue.

### 🔐 For security issues

If you find a **security vulnerability**, do NOT open an issue. Email to [security@answer.dev](mailto:security@answer.dev]) instead.

Nell’issue non sono identificati file, test o punti di ingresso. Chiarisci innanzitutto se le linee guida per l’invio devono essere modificate e dove vengono mantenute, quindi esamina le indicazioni sottoposte a rendering dell’issue GitHub e conferma che la modifica prevista alla documentazione sia completa.

Scritto dal modello di indicizzazione a partire dal testo della issue.