Repository navigation
attribution run 2026 08 19
github-actions[bot] edited this page Aug 19, 2026
·
1 revision
Daily community attribution updater completed successfully. Updated README.md and wiki with latest community contributor data.
- Total Community Contributors: 301
- Total Resolved Issues: 1003
- New Contributors: 4 (Dongbumlee, kubaflo, Calidus+1, DeagleGross+1, Etienne-M+1)
- Tier 0 (Direct Issues): 1003 issues with stateReason=COMPLETED
- Tier 1-2 (Merged PRs): Included in attribution_by_author.json
- Tier 3 (Candidates Checked): 2 issues processed
- Tier 4 (Unlinked): 2 issues flagged for review
Both closed with NOT_PLANNED state (declined/won't-fix, not code contributions):
| Author | Issue | Closed | State |
|---|---|---|---|
| @bryanchen-d | #47156 | 2026-07-22 | NOT_PLANNED |
| @jeffhandley | #41994 | 2026-08-02 | NOT_PLANNED |
- ✅ Updated contributor links and counts
- ✅ Added 4 new contributors
- ✅ Added Tier 4 section with 2 unlinked candidates
- 📝 Pull Request:
community-attribution-2026-08-19
- ✅ Compact format referencing full list in README
- ✅ Top 10 contributors by count
- ✅ Git commit:
752eea1
Five-Tier Attribution Strategy:
- Tier 0 (Direct): Issues closed as COMPLETED by issue author (strongest signal)
- Tier 1 (GitHub Native): GitHub close-by references in merged PRs
- Tier 2 (Keywords): Standard closing keywords in PR bodies
- Tier 3 (Cross-ref): GitHub MCP lookups for follow-up/split issues
- Tier 4 (Candidates): Unlinked but closed in review period → flag for maintainer
Pre-fetched data in /tmp/gh-aw/agent/community-data/:
-
attribution_by_author.json— 301 authors, pre-sorted and pre-grouped -
tier3_candidates_capped.json— 2 candidates (capped at 5 per run) -
readme_community_section_tier012.md— Pre-formatted README section
No duplicate community members. All 301 entries are unique contributors.
Status: ✅ Completed
PR Created: Yes (community-attribution-2026-08-19)
Wiki Updated: Yes (compact format, links to README for full list)
Duration: ~2-3 minutes
Content may be AI generated.