BlueGit

timfa filemanager

commuiy

timfa Tim Falken · pushed by timfa

Authored 2026-05-24 · 5 months ago

Hash
37482082aa07c6e7d0931a66fcae91c0652f0cb1
Parent
0fc3c4d3
1 file changed +1 −1
.github/copilot-instructions.md +1 −1
@@ -19,7 +19,7 @@
19 19
20 20 ### Git authoring
21 21 - When starting work on something, create a feature or fix branch
22 - When concrete, complete steps are made, create a commit in that branch as you work
22 - When concrete, complete steps are made, create a commit in that branch as you work. There is no such thing as 'too many commits'
23 23 - Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
24 24 - Keep commit subjects short and to the point (what changed)
25 25 - Include a longer commit description body that explains the change in user-facing terms (what users will notice), not implementation detail
@@ -19,7 +19,7 @@
19
19
20### Git authoring
20### Git authoring
21- When starting work on something, create a feature or fix branch
21- When starting work on something, create a feature or fix branch
22- When concrete, complete steps are made, create a commit in that branch as you work
22- When concrete, complete steps are made, create a commit in that branch as you work. There is no such thing as 'too many commits'
23- Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
23- Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
24- Keep commit subjects short and to the point (what changed)
24- Keep commit subjects short and to the point (what changed)
25- Include a longer commit description body that explains the change in user-facing terms (what users will notice), not implementation detail
25- Include a longer commit description body that explains the change in user-facing terms (what users will notice), not implementation detail