Turn GitHub activity into client-ready project updates

GitHub imports help ClientCadence turn recent development activity into client-ready updates. The integration is read-only and focuses on selected repository metadata: pull request titles and status, issue titles and labels, commit messages, tags and releases, repository names, timestamps, and links.

Use this when technical work is visible in GitHub, but the client needs a clear explanation of progress, blockers, release status, and next steps.

Paid workspaces can use explicit comments such as /clientcadence update, /clientcadence release update, or /cc follow-up in an issue or pull request conversation. ClientCadence replies with a draft for review. It does not comment on normal GitHub activity unless a user writes one of those commands.

Passive webhooks can update internal project signals quietly, so ClientCadence can notice completed work, release signals, blockers, and client-action items without creating noisy GitHub comments.

• It does not auto-comment on every pull request, issue, release, or push.
• It does not create issues, pull requests, commits, tags, or releases.
• It does not edit or delete GitHub comments.
• It does not read source code files, inspect diffs, or analyze patches.
• It does not send anything to clients without user review.

ClientCadence separates completed work from released work so your client update does not overpromise. A merged pull request can mean the work is done, but a release or tag is stronger evidence that it shipped.

That distinction helps avoid telling clients something is live when it was only merged, reviewed, or prepared for the next release.

1. Connect GitHub from Settings on a Pro or Agency workspace.
2. Select the repositories ClientCadence may use as draft context.
3. Link a selected repository to the relevant ClientCadence project.
4. Import recent pull requests, issues, commits, tags, and releases.
5. Optionally use an explicit /clientcadence command in GitHub.
6. Review the imported activity summary.
7. Generate a client-ready update and edit it before sending.
8. Save to History, copy it, or send through Gmail or Slack.

GitHub activity imports are available on Pro and Agency workspaces. Free users can still paste GitHub notes manually and generate drafts under the normal Free limits.

Users choose when to import GitHub activity and when to use it in a draft. Saved History stores compact import metadata, not repository source code or diffs. Review every draft before sending or relying on it.

GitHub activity works best with saved project History. Start with the History guide , read the GitHub project update guide, or review project status email templates for examples of client-facing progress updates.