9 Commits

Author	SHA1	Message	Date
rugk	db2d8f1598	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
R4SAS	617b421d8f	Fix comment in bug report issue template	2023-09-03 19:30:32 +03:00
rugk	876a59cedc	Apprently GitHub ... Apparently GitHub now adds a security policy button by default (this is new, is not it?)? Also they have a policy report form behind that button. So reports can apparently now be made online at GitHub? (IMHO that is fine, just need to be aware of that) As such, IMHO two buttons would be confusing, so let's remove our custom one here?	2023-08-28 18:49:27 +02:00
El RIDO	e89593b4fc	comment fix, kudos @r4sas	2023-08-11 20:51:12 +02:00
rugk	1bb23ef9ca	Remove markdown from issue selector ... Was worth a try, but apparently markdown is not supported there.	2023-08-09 23:11:35 +02:00
rugk	991ec6ca22	Fix potential syntax error in YAML ... Likely that online VSCode did a stupid line wrapping here, let's see whether that works.	2023-08-09 18:19:33 +02:00
rugk	a22b96b7fc	style: fix typo	2023-08-07 20:02:36 +02:00
rugk	204d1756c9	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 17:59:07 +00:00
rugk	1a37f7b865	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