oliviaiii1224/issue_tmp

★ 14Audience · developerComplexity · 1/5Setup · easy

Mindmap

mindmap
  root((repo))
    What it does
      9 issue form types
      PR template included
      Auto-labels on submit
      No blank issues allowed
    Template Types
      Bug reports
      Feature requests
      Task tracking
      Incident tracking
    How to use
      Copy .github folder
      Create labels first
      Org-wide defaults
    Audience
      Software teams
      Chinese-language projects
      Open source maintainers

mindmap root((repo)) What it does 9 issue form types PR template included Auto-labels on submit No blank issues allowed Template Types Bug reports Feature requests Task tracking Incident tracking How to use Copy .github folder Create labels first Org-wide defaults Audience Software teams Chinese-language projects Open source maintainers

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Add structured bug, feature, and task forms to a GitHub project so every issue has the right info from the start.

USE CASE 2

Set organization-wide issue templates so all repos under your account inherit consistent forms automatically.

USE CASE 3

Manage a Traditional Chinese-language open source project with labeled, categorized issue workflows.

USE CASE 4

Track production incidents and UI changes with dedicated issue forms that auto-attach the correct label.

Tech stack

GitHub IssuesYAML issue formsGitHub CLIMarkdown

Getting it running

Difficulty · easy Time to first run · 30min

Copy the .github/ folder to your repo root, then use the GitHub CLI to create all nine labels (names are in Chinese). Labels must exist before templates work correctly.

No license information was mentioned in the explanation.

In plain English

This repository is a ready-to-copy set of GitHub Issue and Pull Request templates written in Traditional Chinese. The goal is to give software teams a consistent format for reporting bugs, requesting features, tracking tasks, and documenting incidents, so that every issue opened in a project contains the same minimum information and gets routed correctly without extra back-and-forth. The collection includes nine distinct issue form types: bug reports, new feature requests, changes to existing features, task tracking, UI and layout adjustments, spike or research investigations, documentation needs, support questions, and production incident tracking. Each template automatically attaches a label and a title prefix when someone submits an issue, which makes filtering and prioritizing easier. Blank issue creation is disabled, so contributors must pick from one of the nine forms. A separate pull request template is also included, with sections for describing what changed, what to watch out for, and what parts of the project are affected. There is also a contributing guide and a code of conduct. To use these templates, you copy the .github/ folder from this repository into your own project's root directory and push it. GitHub automatically detects the folder and shows the forms when anyone opens a new issue. The README also explains how to set these templates as organization-wide defaults, so every repository under an account inherits them without needing individual copies. Because GitHub only applies labels that already exist in a repository, the README includes instructions and GitHub CLI commands to create all nine required labels before the templates will work correctly. The label names are in Chinese to match the form language.

Copy-paste prompts

Prompt 1

I want to add these Traditional Chinese GitHub issue templates to my project. Show me the exact steps to copy the .github/ folder, push it, and create all nine required labels using the GitHub CLI.

Prompt 2

How do I set these issue templates as organization-wide defaults in GitHub so every repository under my account uses them without copying files into each repo?

Prompt 3

I want to customize one of these YAML issue forms, for example, the bug report template, to add an extra required field. Show me how to edit the form and what YAML properties I can use.

Prompt 4

My team opened a new repo and the issue labels don't exist yet, so the templates show warnings. Give me a GitHub CLI script to create all nine labels in one go.

Prompt 5

Translate the label names and title prefixes in these templates from Traditional Chinese to English so my English-speaking team can use the same structured forms.

Open on GitHub → Explain another repo

← oliviaiii1224 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.