Fix input type to textarea and detailed descriptions for body/markdown (1910e52f) · Commits · sc07 / Fedify Patched

.github/ISSUE_TEMPLATE/bug-report.yml

+5 −2

Original line number	Diff line number	Diff line
		@@ -5,9 +5,12 @@ body:
		- type: markdown
		attributes:
		value: \|
		Please fill out the sections below to help us reproduce and fix the issue.
		Focuses on reporting unintended behavior in the system.

		- type: input
		- Requires: Reproducible steps, expected vs. actual behavior, environment details.
		- Goal: Help identify and fix logic or runtime errors.

		- type: textarea
		attributes:
		label: Summary
		description: Describe the issue you're reporting.

+6 −3

Original line number	Diff line number	Diff line
		@@ -5,16 +5,19 @@ body:
		- type: markdown
		attributes:
		value: \|
		Please use this template to report issues or suggestions related to the documentation.
		Focuses on correcting, updating, or creating documentation.

		- type: input
		- Includes: Affected files, what’s missing or incorrect, suggested content.
		- Goal: Improve clarity, completeness, and usefulness of docs.

		- type: textarea
		attributes:
		label: Summary
		description: Briefly describe the documentation issue.
		validations:
		required: true

		- type: input
		- type: textarea
		attributes:
		label: Affected Docs
		description: Specify which documentation needs changes (file, section, etc.).

+17 −3

Original line number	Diff line number	Diff line
		name: "Feature / Enhancement Issue"
		name: "Feature or Enhancement Issue"
		description: "Suggest a new feature or improvement"
		labels: [ "type/feature", "type/enhancement" ]
		body:
		- type: markdown
		attributes:
		value: \|
		Please fill out the following sections to help us understand your feature request.
		### Feature
		A request to add entirely new functionality.

		- type: input
		- Includes: Motivation, proposed solution, and use cases.
		- Goal: Expand capabilities of the system.

		### Enhancement
		An improvement to an existing feature.

		- Includes: Pain points in current behavior and better alternatives.
		- Goal: Improve usability, performance, or completeness.

		---

		Please keep only one appropriate type/* label and remove the others if present.

		- type: textarea
		attributes:
		label: Summary
		description: Briefly describe the feature or enhancement you're suggesting.

+23 −8

Original line number	Diff line number	Diff line
		name: "Maintenance / Chore Issue"
		name: "Maintenance or Chore Issue"
		description: "Track maintenance tasks, build updates, or CI/CD improvements"
		labels: [ "type/maintenance", "type/chore" ]
		body:
		- type: markdown
		attributes:
		value: \|
		Please use this template to describe maintenance or non-functional tasks.
		### Maintenance
		Tasks that keep the codebase stable and healthy.

		- type: input
		- Includes: Dependency updates, cleanup of deprecated code, resolving warnings.
		- Goal: Prevent technical debt and ensure long-term maintainability.

		### Chore
		Non-functional tasks related to configuration, tooling, or infrastructure.

		- Includes: CI/CD changes, build system tweaks, formatting configs.
		- Goal: Improve the development workflow and internal operations.

		---

		Please keep only one appropriate type/* label and remove the others if present.

		- type: textarea
		attributes:
		label: Summary
		description: Briefly describe the task or change you're proposing.
		validations:
		required: true

		- type: input
		- type: textarea
		attributes:
		label: Affected Area
		description: What part of the system or tooling is involved?
		@@ -28,10 +42,11 @@ body:
		validations:
		required: false

		- type: checkboxes
		- type: textarea
		attributes:
		label: Checklist
		description: Steps to complete this task.
		options:
		- label: Step 1
		- label: Step 2
		placeholder: \|
		1.
		2.
		3.

+24 −4

Original line number	Diff line number	Diff line
		name: "Refactor / Performance / Test Issue"
		name: "Refactor or Performance or Test Issue"
		description: "Suggest internal code improvements, optimizations, or test updates"
		labels: [ "type/refactor", "type/performance", "type/test" ]
		body:
		- type: markdown
		attributes:
		value: \|
		Please provide the following details to help evaluate and prioritize this internal change.
		### Refactor
		Internal code restructuring without changing behavior.

		- type: input
		- Includes: Target area, motivation, and risk.
		- Goal: Improve maintainability or readability.

		### Performance
		Optimizations aimed at improving speed or resource usage.

		- Includes: Before/after benchmarks, affected areas.
		- Goal: Make the system faster or more efficient.

		### Test
		Improving or adding test coverage.

		- Includes: Scope, test strategy, and rationale.
		- Goal: Ensure stability and prevent regressions.

		---

		Please keep only one appropriate type/* label and remove the others if present.

		- type: textarea
		attributes:
		label: Summary
		description: Briefly describe the change you're proposing.
		validations:
		required: true

		- type: input
		- type: textarea
		attributes:
		label: Target Area
		description: Which part of the codebase is affected?