refactor: update issue and pull request templates for clarity and consistency

This commit is contained in:
Poyraz Avsever
2026-04-18 21:51:19 +03:00
parent d9f62f861b
commit d3d57b098b
3 changed files with 15 additions and 31 deletions
+3 -5
View File
@@ -18,13 +18,11 @@ What do you want to happen?
What alternatives did you evaluate?
## Acceptance criteria
## Success criteria (optional)
How will we know this is done?
How will we know this request is successful?
- [ ] User value: The proposed change solves the stated problem in an end-to-end user flow.
- [ ] Security and access control: Existing authorization rules are preserved, and no sensitive data is exposed.
- [ ] Verifiability: Completion is proven with test steps, reproducible evidence, or clear output/screenshots.
Describe 1-3 concrete outcomes.
## Non-goals (optional)