Git Summarize Weekly

Trigger Conditions

Execution Steps

1. Calculate Date Range: Calculate the date from this Monday to today using the

   date

   command.
2. Fetch GitHub Events:
   bash

   gh api users/zc277584121/events --paginate --jq '.[]'

   Fetch recent GitHub activity events for the user.
3. Filter and Analyze:
   • Filter events within this week's date range.
   • Exclude by default repositories under the

     zc277584121

     account, only keep contributions to others' repositories.
   • Do not exclude if the user explicitly requests to include their own repositories.
   • Focus on the following event types:

     • PushEvent

       : Code pushes

     • PullRequestEvent

       : PR creation/merge

     • PullRequestReviewEvent

       : PR Reviews

     • IssuesEvent

       : Issue creation/closure

     • IssueCommentEvent

       : Issue comments

     • CreateEvent

       : Branch/tag creation
4. Output Format:
   • Must output in English, suitable for direct copying into weekly reports.
   • List major features or important PRs as individual items with brief descriptions of what was done.
   • Minor fixes, reviews, comments, etc., can be combined into a single item.
   • Group by repository with a concise and clear format.
   • Example format:

     ## Weekly Contributions (2025-01-20 ~ 2025-01-24)
     
     ### milvus-io/pymilvus
     - Implemented hybrid search API with support for multiple vector fields (#xxx)
     - Fixed connection pool timeout issue (#xxx)
     - Reviewed 3 PRs related to batch insert optimization
     
     ### milvus-io/milvus
     - Minor: commented on 2 issues about memory management

Notes

• The GitHub Events API returns a maximum of 300 events from the last 90 days.
• If there is very little activity in a week, report it truthfully.
• The output should be concise and practical, ready to be pasted directly into weekly reports.