[community] Update community contributions in README#22174
Closed
github-actions[bot] wants to merge 1 commit intomainfrom
Closed
[community] Update community contributions in README#22174github-actions[bot] wants to merge 1 commit intomainfrom
github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
Adds the 🌍 Community Contributions table with 5 confirmed attributions linking community-labeled issues to their resolving PRs: - #21630 (@Mossaka) → #21655 sparse-checkout support docs - #21243 (@holwerda) → #21286 github-app auth in dependencies - #20299 (@grahame-white) → #20300 fix gh aw upgrade lock files - #20249 (@mvdbos) → #20301 cross-repo workflow_call validation - #18480 (@JoshGreenslade) → #21993 GHE Cloud data residency docs Also flags 241 community-labeled issues as attribution candidates needing manual review. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
/q in this repo , external contributors are not allowed to create PRs. Instead they create issues, that get tagged with "community", get assigned to a coding agent and integrated in the repo. As such, any community tagged issue closed as completed is considered a contribution. Update the contribution attribution code to account for this and store the data in repo-memory with wiki. |
Contributor
Author
|
🎩 Mission equipment ready! Q has optimized your workflow. Use wisely, 007! 🔫 |
Contributor
Author
Copilot AI
added a commit
that referenced
this pull request
Mar 21, 2026
…store in wiki (#22174) - Add stateReason field to gh issue list query in shared/community-attribution.md - Add Tier 0 attribution for issues closed as COMPLETED (direct issue contributions) - Update Tier 1/2 to skip Tier 0 issues, Tier 4 to exclude Tier 0 from ambiguous candidates - Add direct issue output type in shared attribution output sections - Add repo-memory wiki: true to daily-community-attribution.md for wiki persistence - Add Step 2 to manage Community Contributors wiki page - Update Step 3 README table with direct issue column support - Update Step 5 PR creation to trigger on README or wiki changes - Recompile lock file with make recompile Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> Agent-Logs-Url: https://github.com/github/gh-aw/sessions/f1a0bf6c-eaee-4b75-93cc-1d5ae990ebf2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Community Contributions Update
Automated update to the 🌍 Community Contributions section in
README.md.Changes
Attribution Summary
Used a four-tier attribution strategy against pre-fetched data:
Tier 1 — GitHub-native closing references (from
closing_refs_by_issue.json):@mvdbos) → #20301 — Cross-repoworkflow_callvalidation@grahame-white) → #20300 — Fixgh aw upgradestale lock filesTier 2 — PR body keyword parsing:
@JoshGreenslade) → #21993 — GHE Cloud data residency docs@holwerda) → #21286 —github-app:auth independencies:@Mossaka) → #21655 — Sparse-checkout docs for large monoreposTier 4 — Attribution candidates: 241 community-labeled issues closed in the window (2026-02-26 – 2026-03-21) could not be automatically linked to a merged PR. These are flagged in the README for maintainer review.