From 5aaeaa55c2819b1fb7183048c8d084e8d5b04668 Mon Sep 17 00:00:00 2001 From: Jon Seager Date: Tue, 25 Nov 2025 11:29:03 +0000 Subject: [PATCH] chore: update copliot instructions --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 0e8a06b..bb46b2a 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -35,7 +35,7 @@ In this phase, we iterate on the solution. - When making changes, consider how to break them down into small, understandable commits. - Each commit should represent a single logical change. Provide a concise commit message for each, adhering to the "Conventional Commits" standard. -- Run `cargo check` and `cargo fmt` before committing. +- **Always** run `cargo check`, `cargo test`, `cargo-clippy` and `cargo fmt` and fix any issues before committing. - Always draft the commit message, showing a summary of which changes will be committed, and ask me for confirmation before actually committing.