Chapril/paste.chapril.org-privatebin
Chapril/paste.chapril.org-privatebin
25
1
Fork 0
Code Issues Releases Wiki Activity
73c13af10d
paste.chapril.org-privatebin/.github/ISSUE_TEMPLATE/bug_report.md

53 lines
1.6 KiB
Markdown
Raw Normal View History

Update and create new issue templates for better ctageorisation [128 of 600 issues are just questions and support and this is getting out of hand IMHO](https://github.com/PrivateBin/PrivateBin/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion%2Fsupport), so I thought we need to do something while of course IMHO keeping support in some sense that is vital to an open-source project. Anyway, this here now: * Converts the "one and only issue template" to multiple ones with the new GitHub way, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/ Note this uses mostly the templates they have, modifies them to use proper headers (sorry but I don't get why they always want to use **bold text** as headers, when you have real markdown headings) and adjusts/ports the * We could use even more elaborate issue forms, but that was too much for me to do now and is also beta, so maybe when they have a visual editor for that or so 😉 https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms The aim: * is to get support requests and stuff directly sorted and tagged, so they are out the way * is to nudge people to improve the quality of issues/reports by providing a more useful template or their use case * is to redirect people to the appropriate resource (give me a moment)
2023-08-07 19:24:13 +02:00
---
name: Bug report
refactor: redirect support questions to discussions including form + more links Discussions apparently onyl support forms see, so I quickly used ChatGPT to convert the Markdown file into the YAMl format and after telling the format it seems to have done that in a good eay: https://chat.openai.com/share/99718495-28d0-4382-ab5e-6a4a733c1ccb (maybe GitHub introduced that after end of 2021 hehe, so the LLM could not know that)
2023-08-07 19:56:38 +02:00
about: Create a report to help us improve (only for software bugs)
Update and create new issue templates for better ctageorisation [128 of 600 issues are just questions and support and this is getting out of hand IMHO](https://github.com/PrivateBin/PrivateBin/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion%2Fsupport), so I thought we need to do something while of course IMHO keeping support in some sense that is vital to an open-source project. Anyway, this here now: * Converts the "one and only issue template" to multiple ones with the new GitHub way, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/ Note this uses mostly the templates they have, modifies them to use proper headers (sorry but I don't get why they always want to use **bold text** as headers, when you have real markdown headings) and adjusts/ports the * We could use even more elaborate issue forms, but that was too much for me to do now and is also beta, so maybe when they have a visual editor for that or so 😉 https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms The aim: * is to get support requests and stuff directly sorted and tagged, so they are out the way * is to nudge people to improve the quality of issues/reports by providing a more useful template or their use case * is to redirect people to the appropriate resource (give me a moment)
2023-08-07 19:24:13 +02:00
title: ''
labels: bug
assignees: ''
---
style: fix typo
2023-08-07 20:02:36 +02:00
<!-- Please make sure to **only** use this template when it is about bugs in the PrivateBin PHP project.
refactor: redirect support questions to discussions including form + more links Discussions apparently onyl support forms see, so I quickly used ChatGPT to convert the Markdown file into the YAMl format and after telling the format it seems to have done that in a good eay: https://chat.openai.com/share/99718495-28d0-4382-ab5e-6a4a733c1ccb (maybe GitHub introduced that after end of 2021 hehe, so the LLM could not know that)
2023-08-07 19:56:38 +02:00
Otherwise, for help and support issues e.g. for deployment issues, please go back and chose the appropiate category. -->
Also add FAQ sectiontick box requirement for bug template It's apparently not enough to have in the Q/A, best is we have it here to. The next step would be converting that into the same form like the QA template. After all, it may mostly just be copy paste as it is nearly identical but well…
2023-09-14 00:02:01 +02:00
**Did you use the FAQ section?**
- [ ] Yes, I have read [the FAQ](https://github.com/PrivateBin/PrivateBin/wiki/FAQ) and I found no solution/answer there.
Fix comment in bug report issue template
2023-09-03 18:30:32 +02:00
<!-- Describe the bug: A clear and concise description of what the bug is. -->
Update and create new issue templates for better ctageorisation [128 of 600 issues are just questions and support and this is getting out of hand IMHO](https://github.com/PrivateBin/PrivateBin/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion%2Fsupport), so I thought we need to do something while of course IMHO keeping support in some sense that is vital to an open-source project. Anyway, this here now: * Converts the "one and only issue template" to multiple ones with the new GitHub way, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/ Note this uses mostly the templates they have, modifies them to use proper headers (sorry but I don't get why they always want to use **bold text** as headers, when you have real markdown headings) and adjusts/ports the * We could use even more elaborate issue forms, but that was too much for me to do now and is also beta, so maybe when they have a visual editor for that or so 😉 https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms The aim: * is to get support requests and stuff directly sorted and tagged, so they are out the way * is to nudge people to improve the quality of issues/reports by providing a more useful template or their use case * is to redirect people to the appropriate resource (give me a moment)
2023-08-07 19:24:13 +02:00
## Steps to reproduce
<!-- Tell us how to reproduce the problem. -->
1.
2.
### What happens
### What should happen
## Additional information
<!--
Here you can add screenshots. If the issue is e.g. a client-side issue (= an issue, which happens in your browser) press F12 and copy and paste the console output or add a screenshot.
If you have access to the server log files, also copy them here.
-->
## Basic information
<!-- If you use a public server enter the address of it here. -->
**Server address**:
<!-- The Operation System of your server -->
**Server OS:**
<!-- The webserver running on your server, preferably including the version -->
**Webserver:**
<!-- The version of your browser (when it is a client-side issue) -->
**Browser:**
<!-- The version of PrivateBin, if you use an unstable version paste the commit hash or the GitHub link to the commit here (you can get it by running `git rev-parse HEAD`) -->
**PrivateBin version:**
I can reproduce this issue on <https://privatebin.net>: Yes / No
Copy Permalink