mvhutz/lambda
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add issue templates for Gitea #22

Merged
mvhutz merged 1 commits from feat/issue-template into main 2026-01-13 01:43:37 +00:00
Conversation 0 Commits 1 Files Changed 4 +164
mvhutz commented 2026-01-13 01:40:43 +00:00
Owner
Copy Link

Description

This PR implements issue templates for the lambda repository to improve issue tracking and developer experience.
The templates follow Gitea best practices and provide clear guidance for users when creating issues.
Three distinct templates were created to handle different types of issues: feature requests, bug reports, and general issues.

Changes

Decisions

All templates use Markdown format with YAML frontmatter, following the existing PR template style.
Each template includes pre-populated metadata (title prefix, labels, target branch).
Templates provide inline HTML comments to guide users without cluttering the final issue.
The templates are consistent with conventional commit format (feat:, fix:, etc.).

Benefits

Users will have clear guidance when creating issues, reducing back-and-forth communication.
Issues will be more structured and contain necessary information for developers.
Pre-populated labels and titles ensure consistent issue categorization.
The templates align with the existing PR template style for a cohesive experience.

Checklist

  • Code follows conventional commit format.
  • Branch follows naming convention (<type>/<description>). Always use underscores.
  • Tests pass (if applicable).
  • Documentation updated (if applicable).
## Description This PR implements issue templates for the lambda repository to improve issue tracking and developer experience. The templates follow Gitea best practices and provide clear guidance for users when creating issues. Three distinct templates were created to handle different types of issues: feature requests, bug reports, and general issues. ### Changes - Created [.gitea/ISSUE_TEMPLATE/feature.md](.gitea/ISSUE_TEMPLATE/feature.md) for feature requests and enhancements. - Created [.gitea/ISSUE_TEMPLATE/bug.md](.gitea/ISSUE_TEMPLATE/bug.md) for bug reports. - Created [.gitea/ISSUE_TEMPLATE/general.md](.gitea/ISSUE_TEMPLATE/general.md) for general issues. - Updated [CLAUDE.md](CLAUDE.md) with issue management and workflow documentation. ### Decisions All templates use Markdown format with YAML frontmatter, following the existing PR template style. Each template includes pre-populated metadata (title prefix, labels, target branch). Templates provide inline HTML comments to guide users without cluttering the final issue. The templates are consistent with conventional commit format (feat:, fix:, etc.). ## Benefits Users will have clear guidance when creating issues, reducing back-and-forth communication. Issues will be more structured and contain necessary information for developers. Pre-populated labels and titles ensure consistent issue categorization. The templates align with the existing PR template style for a cohesive experience. ## Checklist - [x] Code follows conventional commit format. - [x] Branch follows naming convention (`<type>/<description>`). Always use underscores. - [x] Tests pass (if applicable). - [x] Documentation updated (if applicable).
mvhutz added 1 commit 2026-01-13 01:40:44 +00:00
feat: add issue templates for Gitea 6436d1e0b8 
Added three issue templates to improve issue tracking:
- Feature request template for new features and enhancements.
- Bug report template for reporting bugs and unexpected behavior.
- General issue template for issues that don't fit other categories.

Templates follow Gitea best practices with proper frontmatter metadata.
Each template includes clear sections with inline comments to guide users.

Updated CLAUDE.md with issue management and workflow documentation.

Closes #21

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
mvhutz merged commit dec9af0244 into main 2026-01-13 01:43:37 +00:00
mvhutz deleted branch feat/issue-template 2026-01-13 01:43:37 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mvhutz
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mvhutz/lambda#22
Delete Branch "feat/issue-template"

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?