Sage_Software/2002-Chevy-Express-1500
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Add timestamp requirement to issue template

Browse Source 
- Updated ISSUE_TEMPLATE.md with stricter timestamp guidelines
- Added requirement: EVERY entry must have timestamp - no exceptions
- Added examples of entries that need timestamps
- Added section on common mistakes to avoid
- Created memory note: /workspace/memory/TIMESTAMP-REQUIREMENT.md
- All future progress.md entries will follow YYYY-MM-DD HH:MM format
This commit is contained in:
John Loper II
2026-03-22 19:49:17 -04:00
parent 269ef92d51
commit 0627004769
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ISSUE_TEMPLATE.md
+8
View File
@@ -220,6 +220,8 @@
**IMPORTANT: All entries MUST include full timestamps (YYYY-MM-DD HH:MM) to track issue progress across multiple days.** **IMPORTANT: All entries MUST include full timestamps (YYYY-MM-DD HH:MM) to track issue progress across multiple days.**
**CRITICAL RULE:** Every single entry in the session log must have a timestamp. No exceptions.
- **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Project initiated, diagnosis started"] - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Project initiated, diagnosis started"]
- **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Diagnostic tests completed, root cause identified"] - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Diagnostic tests completed, root cause identified"]
- **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Parts ordered, awaiting delivery"] - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Parts ordered, awaiting delivery"]
@@ -227,6 +229,12 @@
**Session Log Guidelines:** **Session Log Guidelines:**
- Use full timestamp format: YYYY-MM-DD HH:MM (24-hour format) - Use full timestamp format: YYYY-MM-DD HH:MM (24-hour format)
- **Include timestamp for EVERY action, test, and decision**
- Track when parts were ordered, received, and installed (may span multiple days)
- Note when tests were performed and results observed
- Record when vehicle was test-driven and any issues found
- **This enables accurate troubleshooting timeline and pattern recognition across multiple days**
- **Do not skip timestamps for any entries - even quick notes or observations**
- Include timestamp for EVERY action, test, and decision - Include timestamp for EVERY action, test, and decision
- Track when parts were ordered, received, and installed (may span multiple days) - Track when parts were ordered, received, and installed (may span multiple days)
- Note when tests were performed and results observed - Note when tests were performed and results observed