foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-24 18:09:26 -05:00
Code Issues Activity

docs: use more positive examples for labels

Browse source 
# Conflicts:
#	v1.19/user/issue-tracking-basics.md
This commit is contained in:
wackbyte 2023-06-19 20:54:57 -04:00 committed by Caesar Schinas
parent 1ced97d1f8
commit c915d8113a
No known key found for this signature in database
GPG key ID: AE9108461BEA5ACF
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
user/issue-tracking-basics.md
View file

@ -41,7 +41,7 @@ process of review, discussion and closure, which can be more or less strictly de
based on the project you're contributing to.
The first thing that might happen is that your issue is categorized using labels.
Your issue may be reviewed by the project's maintainer(s) and evaluated whether it, i.e., might be a duplicate or an invalid bug report.
Your issue may be reviewed by the project's maintainer(s) and evaluated whether it, i.e., is a bug report or feature request.
Then, depending on what type of issue it is, there might be additional questions
or a discussion and, if applicable, the implementation of a solution (or the rejection of