feat: add required name field to PR template #7
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: "Default Template"
|
||||
title: "<type>: <description>"
|
||||
---
|
||||
|
||||
@@ -27,6 +28,6 @@ How would this PR improve the codebase/product?
|
||||
## Checklist
|
||||
|
||||
- [ ] Code follows conventional commit format.
|
||||
- [ ] Branch follows naming convention (`<type>/<description>`).
|
||||
- [ ] Branch follows naming convention (`<type>/<description>`). Always use underscores.
|
||||
- [ ] Tests pass (if applicable).
|
||||
- [ ] Documentation updated (if applicable).
|
||||
|
||||
@@ -51,4 +51,4 @@ Use the `tea` CLI (Gitea command-line tool) for PR operations instead of `gh`.
|
||||
|
||||
**Note**: Use `--description` (not `--body`) for PR body content.
|
||||
|
||||
**Creating PRs**: Always create PRs in a branch other than `main`, to the `main` branch unless specified otherwise.
|
||||
**Creating PRs**: Always create PRs in a branch other than `main`, to the `main` branch unless specified otherwise. ALWAYS FOLLOW THE PR TEMPLATE, EXACTLY.
|
||||
|
||||
Reference in New Issue
Block a user