CXP-1130: Correct last-activity examples in connector docs - #30
Conversation
The Sync member last activity section illustrated last activity with examples the GitHub organization audit log does not record. Measured on both include=web and include=all, issue and pull request comments and code reviews produce no audit-log events, so neither can yield a last-activity date. The section already stated correctly that unrecorded activity yields no date, so the page contradicted itself. Replace the example list with administrative actions that are recorded, state explicitly that content activity is not counted, and correct the Git-operations paragraph, whose parenthetical implied reviews and comments would otherwise have produced a date. Docs only; no connector change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pushes are recorded in the organization audit log under the git event category; they are excluded because the feed queries with Include: "web", which the following paragraph already explains. Listing them as not recorded attributed the exclusion to the wrong cause. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Connector PR Review: CXP-1130: Correct last-activity examples in connector docsBlocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0 Review SummaryThe full PR diff was scanned for security and correctness; it touches a single documentation file ( Security IssuesNone found. Correctness IssuesNone found. SuggestionsNone. |
Problem
The Sync member last activity section of
docs/connector.mdxillustrated last activity with examples the GitHub organization audit log does not record:Two of those three examples cannot produce a last-activity date. Measured on both
include=webandinclude=all, issue and pull request comments and code reviews produce no audit-log events at all. Administrative actions do.The same error appeared a second time in the Git-operations paragraph, whose parenthetical (
no PR reviews, comments, or settings changes) read as though reviews and comments would otherwise have counted.The section already stated correctly that unrecorded activity yields no date, so the page contradicted itself: it explained the rule and then gave examples that violate it.
Impact
Silent and user-facing. An organization whose members write and review code but administer nothing enables the feature, sees an empty Last login column for every account, and finds nothing in the docs explaining why — the page named their exact workflow as an example of what counts.
Change
Docs only, one file:
No connector change. The connector surfaces what the audit log returns; only the description of what that covers was wrong.
Notes for the reviewer
Found while validating the last-activity feature on v0.0.18 (FIX-05). That test case passes; this was a separate documentation defect.
Closes CXP-1130
🤖 Generated with Claude Code