Summary
The Sync Shared Documentation workflow can fail in its summary step when the commit message contains single quotes.
Observed behavior
After merging issue #332, the application deployment workflows passed, but Sync Shared Documentation failed in job sync-docs, step Summary with a shell parsing error caused by the merge commit message.
Example triggering message:
Merge branch 'feature/issue-332-scoped-coaching-sessions' into dev
Observed error:
unexpected EOF while looking for matching '''
Expected behavior
The workflow should safely render commit metadata in $GITHUB_STEP_SUMMARY regardless of quotes or other shell-sensitive characters in the commit message.
Likely cause
.github/workflows/sync-shared-docs.yml currently interpolates the commit message into a shell echo command without safe escaping.
Suggested direction
Update the summary step to handle commit messages safely, for example by avoiding raw shell interpolation or by writing the value through a quoting-safe mechanism.
Summary
The
Sync Shared Documentationworkflow can fail in its summary step when the commit message contains single quotes.Observed behavior
After merging issue #332, the application deployment workflows passed, but
Sync Shared Documentationfailed in jobsync-docs, stepSummarywith a shell parsing error caused by the merge commit message.Example triggering message:
Merge branch 'feature/issue-332-scoped-coaching-sessions' into dev
Observed error:
unexpected EOF while looking for matching '''
Expected behavior
The workflow should safely render commit metadata in
$GITHUB_STEP_SUMMARYregardless of quotes or other shell-sensitive characters in the commit message.Likely cause
.github/workflows/sync-shared-docs.ymlcurrently interpolates the commit message into a shellechocommand without safe escaping.Suggested direction
Update the summary step to handle commit messages safely, for example by avoiding raw shell interpolation or by writing the value through a quoting-safe mechanism.