| --- |
| description: | |
| This workflow creates daily repo status reports. It gathers recent repository |
| activity (issues, PRs, discussions, releases, code changes) and generates |
| engaging GitHub issues with productivity insights, community highlights, |
| and project recommendations. |
| |
| on: |
| schedule: daily |
| workflow_dispatch: |
| |
| permissions: |
| contents: read |
| issues: read |
| pull-requests: read |
| |
| network: defaults |
| |
| tools: |
| github: |
| # If in a public repo, setting `lockdown: false` allows |
| # reading issues, pull requests and comments from 3rd-parties |
| # If in a private repo this has no particular effect. |
| lockdown: false |
| |
| safe-outputs: |
| create-issue: |
| title-prefix: "[repo-status] " |
| labels: [report, daily-status] |
| source: githubnext/agentics/workflows/daily-repo-status.md@d19056381ba48cb1f7c78510c23069701fa7ae87 |
| --- |
| |
| # Daily Repo Status |
| |
| Create an upbeat daily status report for the repo as a GitHub issue. |
| |
| ## What to include |
| |
| - Recent repository activity (issues, PRs, discussions, releases, code changes) |
| - Progress tracking, goal reminders and highlights |
| - Project status and recommendations |
| - Actionable next steps for maintainers |
| |
| ## Style |
| |
| - Be positive, encouraging, and helpful 🌟 |
| - Use emojis moderately for engagement |
| - Keep it concise - adjust length based on actual activity |
| |
| ## Process |
| |
| 1. Gather recent activity from the repository |
| 2. Study the repository, its issues and its pull requests |
| 3. Create a new GitHub issue with your findings and insights |
