docs: clarify mandatory git hygiene workflow
This commit is contained in:
@@ -22,9 +22,9 @@ History is minimal (`initial`), so prefer concise, imperative commit subjects an
|
|||||||
|
|
||||||
### Mandatory Workflow Rules
|
### Mandatory Workflow Rules
|
||||||
|
|
||||||
- Before making any code change, the working tree must be clean (`git diff` and `git diff --cached` must be empty).
|
- Before starting any request that requires a code change, the repository must have no open Git changes (`git status --short` must be empty).
|
||||||
- If the working tree is not clean before starting, stop and clarify with the requester before proceeding.
|
- If the working tree is not clean before starting a code change request, stop and clarify with the requester before proceeding.
|
||||||
- After completing a requested code change, always create a commit with a concise, imperative message.
|
- After completing a requested code change, always create a Git commit with a concise, fitting, imperative message.
|
||||||
- After completing a requested code change, always push the new commit immediately to the configured remote branch.
|
- After completing a requested code change, always push the new commit immediately to the configured remote branch.
|
||||||
- Use Windows line endings (`CRLF`) for all text files in this repository.
|
- Use Windows line endings (`CRLF`) for all text files in this repository.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user