StarMirror/PrivateBin
1
0
Fork 0
mirror of https://github.com/PrivateBin/PrivateBin.git synced 2024-03-22 13:10:41 +08:00
Code Issues Projects Releases Wiki Activity
e89593b4fc
PrivateBin/.github/ISSUE_TEMPLATE/bug_report.md

50 lines
1.4 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-08 01:24:13 +08: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-08 01:56:38 +08: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-08 01:24:13 +08:00
title: ''
labels: bug
assignees: ''
---
style: fix typo
2023-08-08 02:02:36 +08: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-08 01:56:38 +08:00
Otherwise, for help and support issues e.g. for deployment issues, please go back and chose the appropiate category. -->
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-08 01:24:13 +08:00
<-- Describe the bug: A clear and concise description of what the bug is. -->
## 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
Reference in New Issue Copy Permalink