Conversation
- Add workflows/weekly-issue-summary.md: weekly issue activity report with trend charts - Add docs/weekly-issue-summary.md: documentation page - Update README.md: add entry under Research, Status & Planning Workflows - Fix docs/link-checker.md: normalize section headings to title case Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dsyme
approved these changes
Feb 22, 2026
dsyme
deleted the
add-weekly-issue-summary-1771726361-e9d28ddbd89912fe
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses Phase 1 (consistency check) and Phase 2 (workflow discovery) from the Daily Repo Goal Achiever task.
Phase 1: Docs Style Fix
Fixed inconsistent section heading capitalization in
docs/link-checker.md. Other docs in the repository use title case for section headings, but link-checker.md used sentence case:## What it does→## What It Does## How it works→## How It Works## When it runs→## When It RunsNote: The README heading hierarchy inconsistency (
## Fault Analysis Workflows/## Code Review Workflowsshould be###) is already being addressed in open PR #178.Phase 2: New Workflow — Weekly Issue Summary
Source: weekly-issue-summary.md in gh-aw
Blog coverage: [Meet the Workflows: Teamwork & Culture]((github.github.io/redacted)
Why it's valuable: Every repository that uses GitHub Issues benefits from a periodic activity summary. This workflow runs every Monday and produces a rich discussion with two embedded trend charts — one showing weekly issue opened/closed activity and one showing issue resolution time trends — along with key insights and recommendations. It requires no codebase knowledge and works out of the box for any repository.
Merge rate: The workflow creates discussions (not PRs), so no direct merge rate is tracked. It produced 5 consistent weekly analysis discussions in the gh-aw repository. The reporting pattern (analysis → discussion → team action) has been highly effective across gh-aw workflows.
Generalization: The original workflow had two project-specific shared imports (
shared/reporting.mdandshared/trends.md) for formatting guidelines and Python chart boilerplate. These have been inlined and simplified into the workflow body as self-contained instructions, and the gh-aw specificsandbox: agent: awffirewall configuration has been removed. The workflow is otherwise completely language- and project-agnostic.Proposed name:
weekly-issue-summaryFiles Changed
docs/link-checker.md— Normalized section heading capitalizationworkflows/weekly-issue-summary.md— The adapted workflowdocs/weekly-issue-summary.md— Documentation pageREADME.md— Added entry under Research, Status & Planning Workflows