windmill/.github/workflows/weekly-pr-summary.yml

name: Weekly PR Summary

on:
  schedule:
    # Every Friday at 8:00 AM UTC
    - cron: "0 8 * * 5"
  workflow_dispatch:
    # Allow manual triggering for testing

jobs:
  weekly-pr-summary:
    runs-on: ubicloud-standard-4
    timeout-minutes: 30
    permissions:
      contents: read
      pull-requests: read
      issues: write
      id-token: write
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Generate Weekly PR Summary
        uses: anthropics/claude-code-action@v1
        with:
          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
          prompt: |
            REPO: ${{ github.repository }}

            Generate a minimalistic weekly summary of ONLY MERGED Pull Requests from the past 7 days.

            ## Your Task:

            1. **Calculate Date Range**:
               - Run: `CUTOFF_DATE=$(date --date='7 days ago' --iso-8601)`
               - Run: `TODAY=$(date --iso-8601)`
               - This gives you the exact 7-day window (store these in variables for use in commands)

            2. **Fetch ONLY Merged PRs from Past Week**:
               - Command: `gh pr list --repo ${{ github.repository }} --state merged --search "merged:>=$CUTOFF_DATE" --limit 100 --json number,title,author,mergedAt,url`
               - This returns ONLY PRs that were merged in the last 7 days
               - The --search flag filters by merge date using GitHub's search syntax
               - **FILTER OUT** any PRs with titles starting with "chore: release" or "chore(release)"

            3. **Gather Details**: For each merged PR, include:
               - PR title (NO links)
               - Author (extract login from author.login in JSON)
               - Brief summary: Use `gh pr view <number> --json body` to get PR description, then extract first paragraph or key points (1-2 sentences max)

            4. **Character Limit Enforcement**:
               - The final summary MUST be under 6000 characters
               - Sort PRs by importance (breaking changes > features > bugfixes > other)
               - If the summary exceeds 6000 characters, include only the most important PRs and add at the end: "and X more PRs" where X is the count of omitted PRs

            5. **Save Summary to Markdown File**: Write the summary to a file for webhook delivery:
               - Save the complete formatted markdown to: `summary.md`
               - Do not commit the file to the repository

            ## Output Format:

            ```markdown
            📊 Week of [Start Date] to [End Date]

            **Total PRs Merged**: X

            **[PR Title]**
            Author: @username
            [1-2 sentence description from PR body]

            [Repeat for each merged PR, sorted by importance]

            and X more PRs
            ```

            ## Important Notes:
            - **CRITICAL**: ONLY include PRs with state "merged" from the last 7 days
            - **CRITICAL**: EXCLUDE all PRs with titles starting with "chore: release" or "chore(release)"
            - **CRITICAL**: Total character count MUST be under 6000 characters
            - Use minimal spacing - single line breaks between PRs
            - NO markdown headers (###, ##) - only bold text for titles
            - NO links to PRs
            - NO merged date in output
            - Use GitHub CLI (`gh`) for all operations
            - Sort PRs by importance: breaking changes > features > bugfixes > other
            - If a PR has no description, write "(No description provided)"
            - Extract meaningful summary from PR body - look for the first paragraph or key bullet points
            - Parse JSON responses carefully using `jq` or similar tools
            - If summary exceeds 6000 chars, truncate less important PRs and add "and X more PRs" at the end

            ## Saving the Markdown Output:
            After generating the markdown summary, save it to a file, BUT DO NOT COMMIT IT TO THE REPOSITORY.

            ## Write Tool Fallback:
            - First, attempt to use the Write tool to create `summary.md` with the markdown content
            - If the Write tool returns ANY error or fails:
              1. Use the Bash tool with the `echo` command instead
              2. Use a heredoc to write the content: `cat > summary.md << 'EOF'` followed by your markdown content and `EOF` on a new line
              3. Example: `cat > summary.md << 'EOF'\n[your markdown content here]\nEOF`
              4. This ensures the file is always created regardless of Write tool issues
            - Verify the file was created by running: `ls -lh summary.md`
          claude_args: |
            --allowedTools "Edit,MultiEdit,Write,Read,Glob,Grep,LS,Bash"

      - name: Send Summary to Windmill
        if: hashFiles('summary.md') != ''
        env:
          WEEKLY_SUMMARY_TOKEN: ${{ secrets.WEEKLY_SUMMARY_TOKEN }}
        run: |
          if [[ -f "summary.md" ]]; then
            echo "Found summary.md, sending to Windmill..."

            # Read the markdown content
            MARKDOWN_CONTENT=$(cat summary.md)

            # Create JSON payload
            PAYLOAD=$(jq -n --arg markdown "$MARKDOWN_CONTENT" '{markdown: $markdown}')

            # Send to Windmill webhook
            RESULT=$(curl -s \
              -H 'Content-Type: application/json' \
              -H "Authorization: Bearer $WEEKLY_SUMMARY_TOKEN" \
              -X POST \
              -d "$PAYLOAD" \
              'https://app.windmill.dev/api/w/windmill-labs/jobs/run/f/f/ai/send_past_week_pr_summaries_to_discord')

            echo "Windmill response:"
            echo -E "$RESULT"
            echo "✅ Summary sent successfully to Windmill!"
          else
            echo "⚠️ Warning: summary.md not found, skipping delivery"
            exit 1
          fi