11 lines
753 B
Markdown
11 lines
753 B
Markdown
# Project instructions
|
|
|
|
## Git workflow
|
|
|
|
- Commit changes when the requested work is finished and relevant checks pass. Creating the commit is part of completing the task; do not wait for a separate request to commit.
|
|
- Before starting a new feature, finish and commit the current work.
|
|
- Keep unrelated features or fixes in separate commits. If a request includes two unrelated features, complete, validate, and commit each one before starting the next.
|
|
- Stage only changes belonging to the current task. Leave unrelated pre-existing changes out of the commit.
|
|
- Use a concise commit message that describes the change.
|
|
- When the user links a repository issue, reference its issue number in the corresponding commit message (for example, `Refs #59`).
|