Answer: Claude Code attributes pull requests by matching Claude Code session activity against the code in each PR, analyzing merged pull requests to determine which code was written with Claude Code assistance. Sessions from 21 days before to 2 days after the PR merge date are considered for attribution matching. Status: Confirmed Entry: tool/claude-code/admin-and-enterprise/pr-attribution Revision: 2 Digest: sha256:a646db58e0e4c55e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:03:15Z Last changed: 2026-11-17T12:22:25Z (line length exclusion: — → 1,000 characters) Last verified: 2026-11-20T12:18:01Z Next check: 2026-11-21T12:18:01Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of attribution method | matching Claude Code session activity against the code in each PR | | [1] | 2026-11-20 time window before merge | 21 days | days | [1] | 2026-11-20 time window after merge | 2 days | days | [1] | 2026-11-20 label | claude-code-assisted | | [1] | 2026-11-20 rewrite threshold | 20% | | [1] | 2026-11-20 line length exclusion | 1,000 characters | characters | [1] | 2026-11-20 Sources: [1] Anthropic. "Track team usage with analytics". https://code.claude.com/docs/en/analytics.md Role: primary. Accessed: 2026-11-20T12:18:01Z Quote: "This is done by matching Claude Code session activity against the code in each PR." (Supports: attribution method) Quote: "Sessions from 21 days before to 2 days after the PR merge date are considered for attribution matching." (Supports: time window before merge, time window after merge) Quote: "Merged pull requests containing Claude Code-assisted lines are labeled as `claude-code-assisted` in GitHub." (Supports: label) Quote: "Code substantially rewritten by developers, with more than 20% difference, is not attributed to Claude Code" (Supports: rewrite threshold) Quote: "Lines over 1,000 characters, which are likely minified or generated" (Supports: line length exclusion) Published: 2026-11-20T02:53:54Z Snapshot SHA-256: 7ce19a64912b5aaebc60b05bd1a258b925784648e125ae38cb98efa1b01f7682 (captured 2026-11-17T12:22:23Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T12:22:25Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:18:01Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:18:01Z Last attempt: 2026-11-20T12:18:01Z Notes and limitations: Extracted automatically from a single official source (section "PR attribution"). Related: https://latestn.com/tool/claude-code/admin-and-enterprise/preinstall-require-plugins How do I pre-install and require plugins for my organization in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/private-marketplace-access How do I grant access to a private Claude Code plugin marketplace for users without a git-host account? https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix How does CLAUDE_CODE_PROCESS_WRAPPER differ from CLAUDE_CODE_SHELL_PREFIX in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway How do I plan Claude Code version upgrades when maintaining an LLM gateway? https://latestn.com/tool/claude-code/admin-and-enterprise/plugin-relevance-field-reference What fields and signals can I use in a Claude Code plugin relevance block, such as working directory, command name, or manifest dependency matching? https://latestn.com/tool/claude-code/admin-and-enterprise/plugin-telemetry-events Which OpenTelemetry events should I use to track Claude Code plugin installs and usage across an organization? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T12:22:25Z | changed | line length exclusion: — → 1,000 characters | [1] 2026-11-17T12:22:25Z | changed | time window after merge: — → 2 days | [1] 2026-11-17T12:22:25Z | changed | time window before merge: — → 21 days | [1] 2026-11-17T12:22:25Z | changed | time window after: 2 days → — | [1] 2026-11-17T12:22:25Z | changed | time window before: 21 days → — | [1] 2026-11-13T03:03:15Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/pr-attribution POST: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/pr-attribution with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/pr-attribution?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Claude Code attribute pull requests to users in analytics? Revision 2, last verified 2026-11-20T12:18:01Z. https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution (accessed 2026-11-21T10:00:25Z). @misc{LatestN_tool_claude_code_admin_and_enterprise_pr_attribution_r2, title = {How does Claude Code attribute pull requests to users in analytics?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution}}, note = {Revision 2; digest sha256:a646db58e0e4c55e; last verified 2026-11-20T12:18:01Z; accessed 2026-11-21T10:00:25Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution