Add automatic PR summary generation for develop branch

[Copilot]

This PR implements automatic pull request summary generation to improve code review efficiency. When pull requests are opened against the develop branch, a GitHub Actions workflow now automatically generates and posts a comprehensive summary of changes as a comment.

What this adds

New GitHub Workflow (.github/workflows/pr-summary.yml)

• Triggers: Automatically runs on pull requests targeting the develop branch
• Permissions: contents:read for repository access and pull-requests:write for commenting
• Smart Updates: Updates existing summary comments instead of creating duplicates

Summary Content

The workflow generates detailed statistics including:

• File Changes: Count of added, modified, deleted, and renamed files
• Line Statistics: Lines added, deleted, and net change calculation
• File Listing: Complete list of changed files with their status
• Git Statistics: Detailed diff output similar to git diff --stat

Example Output

## 📊 Pull Request Summary

### Changes Overview
- **Total files changed:** 2
- **Added files:** 2
- **Modified files:** 0
- **Deleted files:** 0
- **Renamed files:** 0

### Line Changes
- **Lines added:** 163
- **Lines deleted:** 0
- **Net change:** 163 lines

### Files Changed

A .github/README.md
A .github/workflows/pr-summary.yml

Technical Implementation

The workflow uses:

• actions/checkout@v4 with full git history (fetch-depth: 0)
• actions/github-script@v7 for GitHub API integration
• Standard git commands for diff analysis (git diff --name-status, git diff --stat, git diff --numstat)
• Bash scripting for data processing and formatting

Safety & Compatibility

• No Conflicts: Designed to work alongside existing CI workflow without interference
• Secure: Uses only official GitHub actions and built-in GitHub API
• Error Handling: Handles edge cases like empty diffs and missing line counts
• Documentation: Added .github/README.md explaining all workflows

This enhancement will make it easier for reviewers to quickly understand the scope and nature of changes in pull requests to the develop branch.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.