Conversation
Add date information to JSON output of `why` and `issue` commands to
enable tracking the timeline of design decisions. Dates are extracted
from filename patterns (YYYY-MM-DD prefix) with git log fallback.
Breaking change: `issue --format json` output changes from string
arrays to object arrays with {file_path, date} structure.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Integrate snippet feature from develop with date feature from #170. Both date and snippet fields are preserved in IssueDocumentEntry. JSON output always uses object arrays with file_path, date, and optionally snippet when --with-snippet is enabled. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Closes # JSON日付情報付与 (#170)
🤖 Generated with Claude Code