Currently, the SyncService creates filenames for synced issues with a configurable prefix (issue-) to prevent filenames from starting with a number. However, synced release notes (e.g., 10.0.0.md) are created without a prefix, leading to inconsistent naming conventions within the .github directory.
To improve consistency, we should add a configurable prefix for release note filenames, similar to how issue filenames are handled. A prefix like v would be a sensible default.
Acceptance Criteria
- A new configuration property,
releaseFilenamePrefix, is added to the issueSync object in ai/mcp/server/github-workflow/config.mjs. A default value of 'v' should be considered.
- The
#syncReleaseNotes method in SyncService.mjs is updated to use this new prefix when constructing the filename for each release note.
- Example:
v10.0.0.md instead of 10.0.0.md.
Currently, the
SyncServicecreates filenames for synced issues with a configurable prefix (issue-) to prevent filenames from starting with a number. However, synced release notes (e.g.,10.0.0.md) are created without a prefix, leading to inconsistent naming conventions within the.githubdirectory.To improve consistency, we should add a configurable prefix for release note filenames, similar to how issue filenames are handled. A prefix like
vwould be a sensible default.Acceptance Criteria
releaseFilenamePrefix, is added to theissueSyncobject inai/mcp/server/github-workflow/config.mjs. A default value of'v'should be considered.#syncReleaseNotesmethod inSyncService.mjsis updated to use this new prefix when constructing the filename for each release note.v10.0.0.mdinstead of10.0.0.md.