[q] feat(community): track external contributor issues as contributions, store in wiki (#22174)

[github-actions]

Summary

External contributors in this repo cannot create PRs. They file issues instead — a maintainer tags them community, a coding agent implements the fix, and the issue is closed as COMPLETED. This PR updates the attribution workflows to recognize that pattern.

Changes

shared/community-attribution.md

• Added stateReason to the gh issue list JSON fields so we can distinguish COMPLETED vs NOT_PLANNED closures
• Added Tier 0 attribution: any community-labelled issue with stateReason == "COMPLETED" is a confirmed contribution by the issue author — no PR linkage required
• Updated Tier 4 (ambiguous candidates) to exclude issues already caught by Tier 0
• Updated the output section to include the new direct issue attribution type (no PR suffix)

daily-community-attribution.md

• Added repo-memory: wiki: true to persist an all-time Community Contributors wiki page
• Added Step 2 to the workflow: read the existing wiki page at /tmp/gh-aw/repo-memory-default/Community-Contributors.md, merge in new contributions without duplicating rows, and write it back
• Updated Step 3 (README table) to show direct issue attribution for Tier 0 contributions (no "Resolved By" PR column)
• Updated Step 5 (PR creation) to trigger when either README or wiki changed
• Updated description and pre-fetched data exploration commands to include stateReason

Wiki Page Format

# Community Contributors

| Issue | Title | Author | Closed | Attribution |
|-------|-------|--------|--------|-------------|
| [#N](url) | Issue title | `@author` | YYYY-MM-DD | direct issue |
| [#N](url) | Issue title | `@author` | YYYY-MM-DD | resolved by #PR |

References

• Triggered by comment on issue [community] Update community contributions in README #22174 by @pelikhan

---

Warning

🛡️ Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files: .github/workflows/daily-community-attribution.lock.yml, .github/workflows/daily-community-attribution.md, .github/workflows/shared/community-attribution.md.

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission. A human must create the pull request manually.

To create a pull request with the changes:

# Download the patch from the workflow run
gh run download 23385718459 -n agent -D /tmp/agent-23385718459

# Create a new branch
git checkout -b q/community-attribution-external-contributors-b977929c77661e20 main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-23385718459/aw-q-community-attribution-external-contributors.patch

# Push the branch and create the pull request
git push origin q/community-attribution-external-contributors-b977929c77661e20
gh pr create --title '[q] feat(community): track external contributor issues as contributions, store in wiki (#22174)' --base main --head q/community-attribution-external-contributors-b977929c77661e20 --repo github/gh-aw

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub min-integrity level.

• [community] Update community contributions in README #22174 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

See Integrity Filtering for more information.

🎩 Equipped by Q · ◷

• expires on Mar 23, 2026, 6:25 PM UTC