respond-to-discussion-features

Respond to Community

Find open GitHub discussions in "Feature Requests & Ideas" that have been resolved by recent releases, and generate draft comments to post.

Arguments

• $ARGUMENTS - Time period to analyze (default: 2months)
• Accepts: Ndays, Nweeks, Nmonths, or ISO date YYYY-MM-DD

Process

Step 1: Setup & Fetch Releases

1. Parse time period from $ARGUMENTS (default: 2months)
2. Create TodoWrite with: Fetch releases | Parse release notes | Fetch discussions | Match features to discussions | Generate output
3. Run gh release list --repo payloadcms/payload --limit 30 to get recent releases
4. Filter to releases within the time period
5. For each release, fetch notes: gh release view <tag> --repo payloadcms/payload --json body -q '.body'

Step 2: Parse Release Notes

1. Extract feature and fix entries from each release:
   • Lines containing feat: or feat(
   • Lines containing fix: or fix(
2. For each entry, capture:
   • PR title (the description text)
   • PR number (from #NNNN pattern)
   • Package scope if present (from feat(scope): pattern)
   • Version it shipped in
3. Build keyword list from titles (feature names, package names, key terms)

Step 3: Fetch Discussions

1. Use GraphQL to paginate through all open Feature Request discussions:

gh api graphql -f query='
{
  repository(owner: "payloadcms", name: "payload") {
    discussions(first: 100, states: OPEN, categoryId: "MDE4OkRpc2N1c3Npb25DYXRlZ29yeTMyMzY4NTUx", orderBy: {field: CREATED_AT, direction: DESC}) {
      pageInfo { hasNextPage endCursor }
      nodes {
        number
        title
        url
        createdAt
        body
      }
    }
  }
}'

1. Continue paginating with after: "<endCursor>" until all discussions fetched
2. Store: number, title, URL, createdAt, body (for matching)

Step 4: Match Features to Discussions

For each feature/fix from releases:

1. Search discussion titles and bodies for keyword matches
2. Consider semantic variations (e.g., "groupBy" matches "group by", "group-by")
3. Filter: only include if discussion was created BEFORE the feature's release date
4. Score matches by keyword overlap
5. Flag ambiguous matches as "Needs Verification"