You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
51 lines
1.3 KiB
51 lines
1.3 KiB
---
|
|
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:
|
|
|
|
safe-outputs:
|
|
create-issue:
|
|
title-prefix: "[repo-status] "
|
|
labels: [report, daily-status]
|
|
source: githubnext/agentics/workflows/daily-repo-status.md@e43596e069e74a65cd7d93315091672d278c2642
|
|
---
|
|
|
|
# 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
|