Create template-issues repo for standardizing issue templates across all repos #10
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Compat/Breaking
Compat/Deprecation
Kind
Bug
Kind
Chore
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Investigation
Kind
Question
Kind
Security
Kind
Testing
Meta/Good First Issue
Meta/Help Wanted
Meta/Stale
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Resolution
Confirmed
Resolution
Duplicate
Resolution
Invalid
Resolution
Won't Fix
Status
Abandoned
Status
Blocked
Status
Needs More Info
Status
Needs Triage
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 25 minutes
Due date
Xeplosion
25 minutes
No due date set.
Dependencies
No dependencies set.
Reference
XeplosionGames/.profile#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What problem does this solve?
Issue templates must be manually copied into every repo since Forgejo does not support org-level template inheritance. Without a dedicated template repo for this, issue templates will drift out of sync across repos over time.
Proposed solution
Create
template-issuesas a minimal Forgejo template repo containing only theISSUE_TEMPLATE/directory andpull_request_template.mdcopied from.forgejo. Every new repo regardless of stack is created from this template first, then the relevant stack template files are added on top.Alternatives considered
Including issue templates in every stack template repo (
template-dotnet,template-script, etc.) — rejected because it creates multiple sources of truth and makes updates harder to propagate.Additional context
No response
Checklist
Create
template-issuesrepo.