kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

chore: replace GitHub templates with Gitea issue/PR templates #116

New Issue
Closed
opened 2026-02-09 15:40:27 +00:00 by forbes · 0 comments
forbes commented 2026-02-09 15:40:27 +00:00
Owner
Copy Link

Summary

The .github/ directory contains issue templates, PR templates, and config inherited from the upstream FreeCAD project. These are GitHub-specific and not used by our Gitea instance. Replace them with Gitea-native templates that match Kindred standards.

Tasks

Remove GitHub-specific files

  • .github/ISSUE_TEMPLATE/config.yml — disables blank issues, links to FreeCAD Forum
  • .github/ISSUE_TEMPLATE/1-FUNCTIONAL_PROBLEM_REPORT.yml — FreeCAD workbench dropdown
  • .github/ISSUE_TEMPLATE/2-CODE_QUALITY_PROBLEM_REPORT.yml — FreeCAD code quality template
  • .github/ISSUE_TEMPLATE/3-BACKPORT_REQUEST.yml — FreeCAD backport template
  • .github/pull_request_template.md — references FreeCAD CONTRIBUTING.md and GitHub
  • .github/FUNDING.yml — FreeCAD GitHub Sponsors config
  • .github/dependabot.yml — GitHub Dependabot (not available on Gitea)
  • .github/labels.yml — FreeCAD label definitions (we manage labels in Gitea directly)

Create Gitea issue templates

Gitea supports YAML issue templates in .gitea/ISSUE_TEMPLATE/. Create templates for:

  • Bug report — reproduction steps, expected vs actual behavior, environment info
  • Feature request — description, use case, proposed implementation
  • Documentation — what needs documenting, where it should go

Create Gitea PR template

  • .gitea/pull_request_template.md — aligned with CONTRIBUTING.md conventions (conventional commits, branch workflow, code style)

Clean up references

  • Review .github/ for any remaining files worth keeping (codespellignore, scripts/, images/) and relocate if needed
  • Update any docs that reference the old GitHub templates

Context

This is a FreeCAD fork hosted on Gitea at git.kindred-systems.com. The GitHub templates reference FreeCAD's upstream contribution workflow, which doesn't apply to Kindred Create.

## Summary The `.github/` directory contains issue templates, PR templates, and config inherited from the upstream FreeCAD project. These are GitHub-specific and not used by our Gitea instance. Replace them with Gitea-native templates that match Kindred standards. ## Tasks ### Remove GitHub-specific files - `.github/ISSUE_TEMPLATE/config.yml` — disables blank issues, links to FreeCAD Forum - `.github/ISSUE_TEMPLATE/1-FUNCTIONAL_PROBLEM_REPORT.yml` — FreeCAD workbench dropdown - `.github/ISSUE_TEMPLATE/2-CODE_QUALITY_PROBLEM_REPORT.yml` — FreeCAD code quality template - `.github/ISSUE_TEMPLATE/3-BACKPORT_REQUEST.yml` — FreeCAD backport template - `.github/pull_request_template.md` — references FreeCAD CONTRIBUTING.md and GitHub - `.github/FUNDING.yml` — FreeCAD GitHub Sponsors config - `.github/dependabot.yml` — GitHub Dependabot (not available on Gitea) - `.github/labels.yml` — FreeCAD label definitions (we manage labels in Gitea directly) ### Create Gitea issue templates Gitea supports YAML issue templates in `.gitea/ISSUE_TEMPLATE/`. Create templates for: - **Bug report** — reproduction steps, expected vs actual behavior, environment info - **Feature request** — description, use case, proposed implementation - **Documentation** — what needs documenting, where it should go ### Create Gitea PR template - `.gitea/pull_request_template.md` — aligned with CONTRIBUTING.md conventions (conventional commits, branch workflow, code style) ### Clean up references - Review `.github/` for any remaining files worth keeping (`codespellignore`, `scripts/`, `images/`) and relocate if needed - Update any docs that reference the old GitHub templates ## Context This is a FreeCAD fork hosted on Gitea at `git.kindred-systems.com`. The GitHub templates reference FreeCAD's upstream contribution workflow, which doesn't apply to Kindred Create.
forbes added the enhancement label 2026-02-09 15:40:27 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
UX
branding
bug
ci/cd
CI/CD workflows and deployment
 defaults
documentation
Developer documentation
 enhancement
high-priority
low-priority
theme
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
forbes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/create#116
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?