studio/docs
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

📝(doc) update issue templates (#976)

Browse Source 
Mention of Impress instead of Docs is confusing. Also added some
automatic labelling.

Signed-off-by: virgile-dev <virgile.deville@beta.gouv.fr>
This commit is contained in:
virgile-dev
2025-05-19 11:14:00 +02:00
committed by GitHub
parent 51618ad081
commit 598fb4fa27
3 changed files with 11 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.github/ISSUE_TEMPLATE/Bug_report.md vendored
View File

@@ -1,7 +1,7 @@
--- ---
name: 🐛 Bug Report name: 🐛 Bug Report
about: If something is not working as expected 🤔. about: If something is not working as expected 🤔.
labels: ["bug", "triage"]
--- ---
## Bug Report ## Bug Report
@@ -18,8 +18,8 @@ A clear and concise description of what you expected to happen (or code).
3. And then the bug happens! 3. And then the bug happens!
**Environment** **Environment**
- Impress version: - Docs version:
- Platform: - Instance url:
**Possible Solution** **Possible Solution**
<!--- Only if you have suggestions on a fix for the bug --> <!--- Only if you have suggestions on a fix for the bug -->

6
.github/ISSUE_TEMPLATE/Feature_request.md vendored
View File

@@ -1,7 +1,7 @@
--- ---
name: ✨ Feature Request name: ✨ Feature Request
about: I have a suggestion (and may want to build it 💪)! about: I have a suggestion (and may want to build it 💪)!
labels: ["feature", "triage"]
--- ---
## Feature Request ## Feature Request
@@ -16,8 +16,8 @@ A clear and concise description of what you want to happen. Add any considered d
A clear and concise description of any alternative solutions or features you've considered. A clear and concise description of any alternative solutions or features you've considered.
**Discovery, Documentation, Adoption, Migration Strategy** **Discovery, Documentation, Adoption, Migration Strategy**
If you can, explain how users will be able to use this and possibly write out a version the docs (if applicable). If you can, explain how users will be able to use this and possibly write out some documentation (if applicable).
Maybe a screenshot or design? Maybe add a screenshot or design?
**Do you want to work on it through a Pull Request?** **Do you want to work on it through a Pull Request?**
<!-- Make sure to coordinate with us before you spend too much time working on an implementation! --> <!-- Make sure to coordinate with us before you spend too much time working on an implementation! -->

14
.github/ISSUE_TEMPLATE/Support_question.md vendored
View File

@@ -1,17 +1,13 @@
--- ---
name: 🤗 Support Question name: 🤗 Support Question
about: If you have a question 💬, or something was not clear from the docs! about: If you have a question 💬, or something was not clear from the docs!
labels: ["support", "triage"]
--- ---
## Support request
**Checks before filing**
Please make sure you have read our [main Readme](https://github.com/suitenumerique/docs).
<!-- ^ Click "Preview" for a nicer view! ^ Also make sure it was not already answered in [an open or close issue](https://github.com/suitenumerique/docs/issues?q=is%3Aissue%20state%3Aopen%20label%3Asupport).
We primarily use GitHub as an issue tracker. If however you're encountering an issue not covered in the docs, we may be able to help! -->
---
Please make sure you have read our [main Readme](https://github.com/numerique-gouv/impress).
Also make sure it was not already answered in [an open or close issue](https://github.com/numerique-gouv/impress/issues).
If your question was not covered, and you feel like it should be, fire away! We'd love to improve our docs! 👌 If your question was not covered, and you feel like it should be, fire away! We'd love to improve our docs! 👌