mirror of
https://github.com/azaion/flights.git
synced 2026-04-22 06:56:30 +00:00
Oleksandr Bezdieniezhnykh
c51cb9b4a5
- Updated coderule.mdc to emphasize readability, meaningful comments, and maintainability. - Revised testing.mdc to set a 75% coverage threshold for business logic and clarified expected results requirements. - Improved clarity in git-workflow.mdc regarding commit message formatting and length. - Added completeness audit requirements in research steps and quality checklists to ensure thoroughness in test specifications. Made-with: Cursor
12 lines
654 B
Plaintext
12 lines
654 B
Plaintext
---
|
|
description: "Git workflow: work on dev branch, commit message format with tracker IDs"
|
|
alwaysApply: true
|
|
---
|
|
# Git Workflow
|
|
|
|
- Work on the `dev` branch
|
|
- Commit message subject line format: `[TRACKER-ID-1] [TRACKER-ID-2] Summary of changes`
|
|
- Subject line must not exceed 72 characters (standard Git convention for the first line). The 72-char limit applies to the subject ONLY, not the full commit message.
|
|
- A commit message body is optional. Add one when the subject alone cannot convey the why of the change. Wrap the body at 72 chars per line.
|
|
- Do NOT push or merge unless the user explicitly asks you to. Always ask first if there is a need.
|