BlueGit

timfa filemanager

Test commit

with extended description

timfa Tim Falken · pushed by timfa

Authored 2026-05-19 · 6 months ago

Hash
5c46b6049563f667b68ab29e41a4c4fb9f592503
Parent
d79d87db
1 file changed +1 −1
.github/copilot-instructions.md +1 −1
@@ -26,7 +26,7 @@
26 26 - Try to commit frequently, chunking work into individual steps
27 27 - When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
28 28 - Ensure you don't leave old branches you've made in git and that everything is merged neatly.
29 - Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
29 - Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
30 30
31 31 ## Testing Expectations
32 32 - **Default rule:** every new feature should receive a test that verifies it behaves as requested.
@@ -26,7 +26,7 @@
26- Try to commit frequently, chunking work into individual steps
26- Try to commit frequently, chunking work into individual steps
27- When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
27- When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
28- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
28- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
29- Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
29- Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
30
30
31## Testing Expectations
31## Testing Expectations
32- **Default rule:** every new feature should receive a test that verifies it behaves as requested.
32- **Default rule:** every new feature should receive a test that verifies it behaves as requested.