Gitea requires the pull request template to be at .gitea/PULL_REQUEST_TEMPLATE.md (as a file), not in a .gitea/PULL_REQUEST_TEMPLATE/ directory.
This PR moves the template from .gitea/PULL_REQUEST_TEMPLATE/default.md to .gitea/PULL_REQUEST_TEMPLATE.md to ensure it works correctly with Gitea.
Benefits
The pull request template will now be automatically loaded when creating new PRs in Gitea.
Follows Gitea's documented convention for PR templates.
## Description
Gitea requires the pull request template to be at `.gitea/PULL_REQUEST_TEMPLATE.md` (as a file), not in a `.gitea/PULL_REQUEST_TEMPLATE/` directory.
This PR moves the template from `.gitea/PULL_REQUEST_TEMPLATE/default.md` to `.gitea/PULL_REQUEST_TEMPLATE.md` to ensure it works correctly with Gitea.
## Benefits
- The pull request template will now be automatically loaded when creating new PRs in Gitea.
- Follows Gitea's documented convention for PR templates.
## Checklist
- [x] Code follows conventional commit format.
- [x] Branch follows naming convention (`<type>/<description>`).
- [x] Tests pass (if applicable).
- [x] Documentation updated (if applicable).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Gitea requires the pull request template to be at
.gitea/PULL_REQUEST_TEMPLATE.md(as a file), not in a.gitea/PULL_REQUEST_TEMPLATE/directory.This PR moves the template from
.gitea/PULL_REQUEST_TEMPLATE/default.mdto.gitea/PULL_REQUEST_TEMPLATE.mdto ensure it works correctly with Gitea.Benefits
Checklist
<type>/<description>).