## Description Gitea requires a `name` field in the frontmatter of pull request templates. This PR adds the required `name: "Default Template"` field to fix the template validation error. Additionally updates CLAUDE.md to reference the PR template format and use lowercase for PR title placeholder. ## Benefits - The pull request template is now valid and will be properly loaded by Gitea. - Users creating PRs will see the template automatically populated. - CLAUDE.md now documents the PR template format for consistency. ## Checklist - [x] Code follows conventional commit format. - [x] Branch follows naming convention (`<type>/<description>`). - [x] Tests pass (if applicable). - [x] Documentation updated (if applicable). Reviewed-on: #7 Co-authored-by: M.V. Hutz <git@maximhutz.me> Co-committed-by: M.V. Hutz <git@maximhutz.me>
34 lines
663 B
Markdown
34 lines
663 B
Markdown
---
|
|
name: "Default Template"
|
|
title: "<type>: <description>"
|
|
---
|
|
|
|
## Description
|
|
|
|
<!--
|
|
First, describe the context for the PR.
|
|
Then, explain why the PR exists.
|
|
Finally, in concise, sentence-long bullets, explain each change.
|
|
-->
|
|
|
|
### Decisions
|
|
|
|
<!--
|
|
List any major architectural decisions here.
|
|
If none exist, omit this section.
|
|
-->
|
|
|
|
## Benefits
|
|
|
|
<!--
|
|
List any major benefits here.
|
|
How would this PR improve the codebase/product?
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
- [ ] Code follows conventional commit format.
|
|
- [ ] Branch follows naming convention (`<type>/<description>`). Always use underscores.
|
|
- [ ] Tests pass (if applicable).
|
|
- [ ] Documentation updated (if applicable).
|