coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions 1 Projects 12 Releases 1 Wiki Activity

GAMEPLAN and DIARY files to subdirectory history #47

New Issue
Closed
opened 2025-09-30 22:01:48 +00:00 by tegwick · 0 comments
tegwick commented 2025-09-30 22:01:48 +00:00
Owner
Copy Link

I want to keep finished gameplans for nostalgic reasons. This also provides the option to do a review and look for inefficient software development patterns to avoid in the future.

We also established the habit to document relevant progress like milestones or workpackages with a high level Diary entry of what has been achieved since the last diary entry.

Both of those files should stick to a reasonable naming scheme and be consolidated in a single directory called history.

The director diary can then be removed.

It might be convenient to have a subagent specific to organizing the history documentation for the project and help keep the repo tidy.

I want to keep finished gameplans for nostalgic reasons. This also provides the option to do a review and look for inefficient software development patterns to avoid in the future. We also established the habit to document relevant progress like milestones or workpackages with a high level Diary entry of what has been achieved since the last diary entry. Both of those files should stick to a reasonable naming scheme and be consolidated in a single directory called history. The director diary can then be removed. It might be convenient to have a subagent specific to organizing the history documentation for the project and help keep the repo tidy.
tegwick added this to the Clean Repository Standard project 2025-09-30 22:01:48 +00:00
tegwick changed title from Move all gameplans to a subdirectory gameplans to GAMEPLAN and DIARY files to subdirectory history 2025-10-01 20:20:31 +00:00
tegwick moved this to Done in Clean Repository Standard on 2025-10-04 22:59:02 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project Clean Repository Standard
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#47
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?