[copilot-pr-merged-report] Daily Copilot PR Merged Report - 2025-12-11

[github-actions[bot]]

Summary

Analysis Period: Last 24 hours (2025-12-10 to 2025-12-11)
Status: ⚠️ Unable to complete analysis due to GitHub API connectivity issues

Issue Encountered

The report generation failed due to HTTPS connectivity problems with the GitHub API. The safeinputs-gh tool encountered the following error:

http: server gave HTTP response to HTTPS client

This appears to be caused by proxy configuration in the execution environment (`HTTPS_PROXY=(redacted)), which is causing the GitHub CLI to receive HTTP responses when expecting HTTPS.

Attempted Operations

The following operations were attempted but failed:

• ❌ List merged pull requests with gh pr list
• ❌ Query GitHub REST API with gh api
• ✅ Verify gh CLI version (2.83.1) and authentication

Impact

Unable to generate the following metrics for merged Copilot PRs:

• Number of merged PRs in the last 24 hours
• Total lines of code added/deleted
• Test files modified
• Workflow execution time and resource usage

Technical Details

Environment Configuration

HTTPS_PROXY=(redacted)
HTTP_PROXY=(redacted)
SQUID_PROXY_HOST=squid-proxy
SQUID_PROXY_PORT=3128

GitHub CLI Version

gh version 2.83.1 (2025-11-13)

Error Message

Post "https://api.github.com/graphql": http: server gave HTTP response to HTTPS client
Get "https://api.github.com/repos/githubnext/gh-aw/pulls?state=closed&per_page=100": http: server gave HTTP response to HTTPS client

Possible Solutions

1. Fix proxy configuration: Ensure the proxy properly handles HTTPS requests
2. Bypass proxy for GitHub API: Add api.github.com to no_proxy environment variable
3. Use different authentication method: Consider using GitHub API tokens directly with curl
4. Investigate safe-inputs wrapper: Check if the /tmp/gh-aw/safe-inputs/gh.sh wrapper script needs proxy configuration updates

Next Steps

1. Investigate and resolve the proxy configuration issue in the workflow execution environment
2. Re-run this report once connectivity is restored
3. Consider adding connectivity checks before attempting API calls

---

Note: This is an automated report. The GitHub API connectivity issue prevents data collection and analysis. Manual investigation of the proxy configuration is required to restore functionality.

---

Generated by Copilot PR Merged Report (Run: Unable to determine workflow run ID due to API connectivity issues)

AI generated by Daily Copilot PR Merged Report

[github-actions[bot]]

⚓ Avast! This discussion be marked as outdated by Daily Copilot PR Merged Report.
🗺️ A newer treasure map awaits ye at Discussion #6275.
Fair winds, matey! 🏴‍☠️