Split issue templates#999
No reviewers
Labels
No labels
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✅ Fixed
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🌐 Translation
🌠 Long-term
🎉 Feature
🎯 Enhancement
🏗️ Build
🐛 Bug
👋 Good-first-issue
💀 Deprecation
💡 Suggestion
💬 Discussion
💭 Brainstorming
💰 Sponsored
💻 UI/UX
📄 Documentation
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
📡 Needs-feedback
📱 F-droid
📸 Release
🔒 Security
🔙 Backport
🔙 Has-backport
🔙 Needs-backport
🔙 Regression
🔭 Cannot-reproduce
🗄️ Repository
🗒️ Changelog
🗓️ Summary
🤾 Google-play
🥑 Ready
🧪 Testing
🧺 Cleanup
🧺 Needs-cleanup
🧾 Confirmed
🩹 External-dependecy
🪒 Refactor
🪜 Upstream
🙇♂️ Needs-help
🚀 Improvement
🚨 Investigate
🛡️ Blocked
🛰️ API-dependency
🟦 Website
No milestone
No project
No assignees
2 participants Notifications
Due date No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#999
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch ":issue-templates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split the issue templates into
Bug
,Feature
andSuggestion
.Can you point to the Gitea doc for this?
https://docs.gitea.io/en-us/issue-pull-request-templates/#issue-template-directory
@ -0,0 +4,4 @@
about: "A new feature or an enhancement to an existing feature"
labels:
- Enhancement
This should change to
Feature
.Changed it, even if the problem would be that most
Feature
s are actually moreEnhancement
s, we'll have to change it. I didn't want to add another new templateEnhancement
since I thought it may be a bit complex for end users to understand what's the diff between aFeature
and anEnhancement
.I guess Feature is fine, we can change it anytime.