feat: archive closed tickets for large stores - #67
Open
johnurbanik wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
tk archive [id...]andtk archive --reindextk closedSIGPIPE failures on stores with more than 100 filesWhy
Large repositories pay the cost of opening every closed ticket for routine graph reads. The Glass had 1,244 ticket files, including 946 closed tickets, causing multi-second Windows/MSYS command latency.
Impact
Closed history remains intact while ready, blocked, show, and graph commands scan only active Markdown files plus one compact index. Relationship edits require reopening an archived ticket to keep the index authoritative.
Validation