Currently, the IssueSyncer generates markdown files where metadata (like the author and sub-issue lists) is duplicated in both the YAML frontmatter and the visible markdown body. This creates bloated files and requires complex logic to strip this redundant information before pushing updates back to GitHub.
This ticket proposes refactoring the IssueSyncer to treat the frontmatter as the single source of truth for all metadata, with the exception of a human-readable progress summary.
Acceptance Criteria:
- Modify
#formatIssueMarkdown in IssueSyncer.mjs to stop generating the Reported by: and Sub-Issues: sections in the markdown body.
- The
**Progress:** ... line should be retained in the body for at-a-glance readability.
- Simplify the body-cleaning logic in
pushToGitHub to reflect that only the Reported by: line and title need to be stripped before pushing.
- The resulting local markdown files will be cleaner, containing only the issue title, the progress summary (if applicable), and the core body content.
Currently, the
IssueSyncergenerates markdown files where metadata (like the author and sub-issue lists) is duplicated in both the YAML frontmatter and the visible markdown body. This creates bloated files and requires complex logic to strip this redundant information before pushing updates back to GitHub.This ticket proposes refactoring the
IssueSyncerto treat the frontmatter as the single source of truth for all metadata, with the exception of a human-readable progress summary.Acceptance Criteria:
#formatIssueMarkdowninIssueSyncer.mjsto stop generating theReported by:andSub-Issues:sections in the markdown body.**Progress:** ...line should be retained in the body for at-a-glance readability.pushToGitHubto reflect that only theReported by:line and title need to be stripped before pushing.