upstream/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2026-05-28 11:14:54 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

markdown fix

Browse source
This commit is contained in:
Otto Richter 2026-04-06 02:39:51 +02:00 committed by Otto Richter
parent 9cf22117e7
commit d4407e7cc5
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.forgejo/issue_template/1-triaging.yaml
View file

@ -21,7 +21,7 @@ body:
We are introducing **a new workflow** to manage issues and understand your problems and needs.
<details><summary>**Instructions for your first problem report**</summary>
<details><summary><b>Instructions for your first problem report</b></summary>
* Focus on **your problem**.
* Take some time to describe your situation.

2
.forgejo/issue_template/2-research.yaml
View file

@ -17,7 +17,7 @@ body:
We are introducing **a new workflow** to manage issues and understand your problems and needs.
Want to report a bug or request a feature? Please follow step 1 instead.
<details><summary>**Instructions for research tasks**</summary>
<details><summary><b>Instructions for research tasks</b></summary>
* Why should this be researched (motivation)?
* What questions should be answered? What information is missing?

2
.forgejo/issue_template/3-design.yaml
View file

@ -17,7 +17,7 @@ body:
We are introducing **a new workflow** to manage issues and understand your problems and needs.
Want to report a bug or request a feature? Please follow step 1 instead.
<details><summary>**Instructions for design units**</summary>
<details><summary><b>Instructions for design units</b></summary>
* What ideas have already been loosely agreed on?
* What needs to be discussed and clarified ...

2
.forgejo/issue_template/4-implementation.yaml
View file

@ -17,7 +17,7 @@ body:
We are introducing **a new workflow** to manage issues and understand your problems and needs.
Want to report a bug or request a feature? Please follow step 1 instead.
<details><summary>**Instructions for implementation tasks**</summary>
<details><summary><b>Instructions for implementation tasks</b></summary>
* This task must be actionable to developers, without anticipating further UX design discussion.
* It is either trivial (e.g. fixing a bug) ...