[WIP] Update daily news agentic workflows to generate trend charts #3012
Conversation
- Added upload-assets safe output to both daily-news.md and daily-repo-chronicle.md - Added comprehensive chart generation instructions for 2 trend charts - Chart 1: Issues & Pull Requests Activity (multi-line chart) - Chart 2: Commit Activity & Contributors (dual-axis chart) - Imported shared/trends.md for trend visualization guidance - Added GitHub API tools configuration for data collection - Python environment and libraries already available via shared/python-dataviz.md - Workflows compile successfully and tests pass Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
This pull request adds trend chart visualization capabilities to two daily reporting workflows (daily-repo-chronicle and daily-news). The changes enable AI agents to generate and embed data visualization charts showing repository metrics like issues, PRs, and commit activity over time.
Key changes:
- Adds
upload-assetssafe output configuration for uploading chart images to a Git branch - Integrates Python data visualization libraries (NumPy, Pandas, Matplotlib, Seaborn) via shared imports
- Adds detailed chart generation instructions requiring exactly 2 trend charts per report
- Implements a new
upload_assetsjob to publish generated charts to orphaned Git branches - Adds cache-memory support for storing reusable Python helper functions
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
.github/workflows/daily-repo-chronicle.md |
Adds chart requirements, imports trends/python-dataviz modules, configures upload-assets output |
.github/workflows/daily-repo-chronicle.lock.yml |
Compiled workflow with Python setup, asset upload job, cache-memory configuration |
.github/workflows/daily-news.md |
Similar chart visualization additions with GitHub API toolset configuration |
.github/workflows/daily-news.lock.yml |
Compiled workflow matching daily-news.md changes |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| **Phase 4: Upload Charts** | ||
|
|
||
| 1. Upload both charts using the `upload asset` tool |
There was a problem hiding this comment.
The instruction refers to 'upload asset' tool but the actual configuration uses 'upload-assets' (hyphenated). This inconsistency could confuse users about which tool name to use. Recommend standardizing on either 'upload-assets' or 'upload_asset' throughout.
| 1. Upload both charts using the `upload asset` tool | |
| 1. Upload both charts using the `upload-assets` tool |
| ## 📊 Trend Charts Requirement | ||
|
|
||
| **IMPORTANT**: Generate exactly 2 trend charts that showcase key metrics of the project. These charts should visualize trends over time to give readers a visual representation of the repository's activity patterns. | ||
|
|
There was a problem hiding this comment.
[nitpick] The requirement for 'exactly 2 trend charts' is rigid but lacks explanation of what happens if the AI generates fewer or more charts. Consider adding guidance on error handling or validation of chart count.
| **Validation and Error Handling**: After generating the charts, validate that there are exactly 2 trend charts included in your output. If there are fewer than 2 charts, attempt to regenerate or supplement the missing chart(s) and clearly report the issue in your output. If there are more than 2 charts, remove the extras and note the correction. Always include a brief summary in your report indicating whether the chart count validation passed or if any corrective action was taken. |
| allowed: | ||
| - list_pull_requests | ||
| - list_issues | ||
| - list_commits | ||
| - get_pull_request | ||
| - issue_read | ||
| - search_issues | ||
| - search_pull_requests | ||
| - list_discussions |
There was a problem hiding this comment.
When using toolsets (which enable groups of tools), explicitly listing individual tools in 'allowed' creates redundancy. The 'default' toolset already includes most of these tools. Either remove the 'allowed' section and rely on toolsets, or remove 'toolsets' and use only the explicit 'allowed' list for clarity.
| allowed: | |
| - list_pull_requests | |
| - list_issues | |
| - list_commits | |
| - get_pull_request | |
| - issue_read | |
| - search_issues | |
| - search_pull_requests | |
| - list_discussions |
Update Daily News Workflows with Trend Charts ✅
Summary
Successfully implemented trend chart generation for daily news agentic workflows as requested. Both workflows now generate exactly 2 professional trend charts showcasing key repository metrics.
Implementation Complete
Workflows Updated
Chart Specifications
Chart 1: Issues & Pull Requests Activity
Chart 2: Commit Activity & Contributors
Quality Standards
Five-Phase Execution
Infrastructure Leveraged
Verification Results
Changes
.github/workflows/daily-news.md(+124 lines).github/workflows/daily-news.lock.yml(+362 lines).github/workflows/daily-repo-chronicle.md(+107 lines).github/workflows/daily-repo-chronicle.lock.yml(+1285 lines)Impact
When workflows execute, they will:
✨ Automatically collect repository metrics
✨ Generate 2 professional trend charts per report
✨ Upload charts as accessible assets
✨ Embed visualizations with analysis in discussions
✨ Provide visual insights into project health and activity
The workflows are production-ready and will enhance daily reporting with data-driven visualizations.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.