Reorder issue templates and automatically add labels #18875
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
delvh
added
type/docs
Gusted
approved these changes
Feb 25, 2022
GiteaBot
added
the
lgtm/need 1
| @@ -1,5 +1,6 @@ | |||
| name: Feature Request | |||
| description: Got an idea for a feature that Gitea doesn't have currently? Submit your idea here! | |||
| labels: kind/feature | |||
There was a problem hiding this comment.
Well, the problem I have with that is:
What exactly is the difference between feature and proposal?
I've seen both used, but for me, they mean pretty much the same thing.
I mean, I can add it, but aren't these two labels simply duplicates? Or do I understand something wrong?
There was a problem hiding this comment.
I've added it now. However, I still would like to know the difference between kind/proposal and kind/feature.
jpraet
reviewed
Feb 27, 2022
|
Ping, @jpraet @techknowlogick |
jpraet
approved these changes
Feb 28, 2022
GiteaBot
added
lgtm/done
|
make L-G-T-M work. |
a1012112796
added a commit
to a1012112796/gitea
that referenced
this pull request
Mar 21, 2022
* main: Reorder issue templates and automatically add labels (go-gitea#18875) Use IterateBufferSize whilst querying repositories during adoption check (go-gitea#19140) Add 1.18 (go-gitea#19151) [skip ci] Updated translations via Crowdin Fix NPE `/repos/issues/search` when not signed in (go-gitea#19154)
|
finally 😌 |
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Mar 22, 2022
* giteaofficial/main: Fix the bug: deploy key with write access can not push (go-gitea#19010) Renamed ctx.User to ctx.Doer. (go-gitea#19161) [docs] Enhance container selection in docker dump (go-gitea#14292) Cleanup protected branches when deleting users & teams (go-gitea#19158) Reorder issue templates and automatically add labels (go-gitea#18875) Use IterateBufferSize whilst querying repositories during adoption check (go-gitea#19140)
Chianina
pushed a commit
to Chianina/gitea
that referenced
this pull request
Mar 28, 2022
* Reorder bug-report.yaml * Add bug label on bug-report.yaml * Add feature label on feature-request.yaml * Reorder ui.bug-report.yaml * Apply suggestions Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: zeripath <art27@cantab.net>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It annoyed me that the issue description which is the most vital part of an issue was displayed at the end, resulting in long scrolling.
Hence, I reordered the issue templates so that the information I deem most relevant is displayed at the top.
Apart from the description, this includes a relocation of the "Can you confirm this on try.gitea.io?" question and of the logs and screenshots.
Additionally, I added applicable labels on each template so that every bug will be auto-labeled
kind/bug, and every feature request will automatically be labeledkind/feature.