Skip to content

feat: add release tracking to comment summary template#3

Merged
mmcky merged 4 commits intofeat/comment-summary-templatefrom
feat/release-tracking
Feb 23, 2026
Merged

feat: add release tracking to comment summary template#3
mmcky merged 4 commits intofeat/comment-summary-templatefrom
feat/release-tracking

Conversation

@mmcky
Copy link
Contributor

@mmcky mmcky commented Feb 23, 2026

Summary

Adds release tracking to both the main report and the comment summary template.

Changes

Report Table — Releases Column

  • New Releases column between Merged PRs and Commits
  • Count of non-draft releases published in the report date range
  • Clickable link to the repo's releases page when count > 0
  • Included in totals row, Details section, and summary output
  • Works for both org repos and external tracked repos

Comment Template — Releases Table

  • Consolidated releases table at the top of the template (before PR listings)
  • Columns: Repository, Release (name/tag with link), Date
  • Sorted by publication date (newest first)
  • Section omitted entirely when no releases in the period
  • PR listings per repo remain unchanged below

API

  • Fetches /repos/{org}/{repo}/releases unconditionally (one call per active repo)
  • Filters to non-draft releases with published_at within the date range

Testing

Tested with --start=2026-02-01 --end=2026-02-23:

  • 35 releases across 13 repos in the report table
  • 95 merged PRs across 33 active repos (unchanged)
  • Comment template: releases table at top, PR listings below, no duplication

Depends On

- Fetch releases published in the report date range via GitHub API
- Display releases with 📦 emoji at top of each repo section, before PRs
- Include release name, tag, and link to GitHub release page
- Works for both organization repos and external tracked repos
- Update docs and CHANGELOG with release tracking details
- Auto-detect contributors and use markdown links (carried from template branch)
- Replace per-repo inline release bullets with a single consolidated table
- Table columns: Repository, Release (name/tag with link), Date
- Sorted by publication date (newest first)
- Releases section omitted entirely when no releases in the period
- PR listings per repo remain unchanged below the table
- Update docs example and CHANGELOG
- Fetch releases unconditionally (not just when summary-template enabled)
- Add Releases column between Merged PRs and Commits in report table
- Release count links to repo's releases page when > 0
- Include in totals row and Details section
- Add to external repos table and totals
- Include in summary string output
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds release tracking to the weekly activity report and to the generated comment summary template, so maintainers can surface published releases alongside PR/issue/commit activity.

Changes:

  • Adds a Releases metric/column to the main report (including totals, details, and external repos section).
  • Fetches and counts non-draft releases within the report date range for each repo.
  • Extends the comment summary template to include a consolidated releases table (sorted newest-first) above per-repo PR listings.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File Description
generate-report.sh Fetches releases per repo, adds releases to report tables/totals/summary, and emits a releases table in the summary template.
docs/comment-summary-template.md Updates documentation and example output to describe/illustrate the new releases table in the template.
CHANGELOG.md Adds an Unreleased entry describing the new release tracking behavior (currently focused on the template).

- Add rate_limited_repos/failed_repos error handling for releases API call
- Use cross-platform date formatting (GNU first, BSD fallback)
- Remove unused all_template_repos dead code block
- Add CHANGELOG entry for Releases column in main report table
@mmcky mmcky merged commit e94b6e9 into feat/comment-summary-template Feb 23, 2026
mmcky added a commit that referenced this pull request Feb 23, 2026
* feat: add comment summary template for activity report highlights

- New --summary-template flag and summary-template action input
- Collects merged PR titles, URLs, authors, and labels during processing
- Generates comment-template.md with PRs grouped by repository
- Includes placeholder sections for human-written thematic summaries
- Labels displayed in brackets to aid categorization
- New comment-template action output for downstream workflow steps
- Works with both org repos and external repositories
- Added docs/comment-summary-template.md with usage guide

* docs: add auto-post workflow for comment summary template

Update example workflow in README and feature docs to show the full
3-step flow: generate report + template, create issue, then post the
template as the first comment using peter-evans/create-or-update-comment.

* feat: auto-detect contributors from PRs and use markdown links

- Extract unique non-bot authors from merged PR data
- Format as 'thanks @user1, @user2, and @user3...' acknowledgement
- Filter out [bot] accounts and Copilot from contributor list
- Use markdown link format [PR Title](url) for clean GitHub rendering

* feat: add release tracking to comment summary template (#3)

* feat: add release tracking to comment summary template

- Fetch releases published in the report date range via GitHub API
- Display releases with 📦 emoji at top of each repo section, before PRs
- Include release name, tag, and link to GitHub release page
- Works for both organization repos and external tracked repos
- Update docs and CHANGELOG with release tracking details
- Auto-detect contributors and use markdown links (carried from template branch)

* refactor: use single releases table at top of template (Option A)

- Replace per-repo inline release bullets with a single consolidated table
- Table columns: Repository, Release (name/tag with link), Date
- Sorted by publication date (newest first)
- Releases section omitted entirely when no releases in the period
- PR listings per repo remain unchanged below the table
- Update docs example and CHANGELOG

* feat: add Releases count column to report table

- Fetch releases unconditionally (not just when summary-template enabled)
- Add Releases column between Merged PRs and Commits in report table
- Release count links to repo's releases page when > 0
- Include in totals row and Details section
- Add to external repos table and totals
- Include in summary string output

* fix: address Copilot review feedback

- Add rate_limited_repos/failed_repos error handling for releases API call
- Use cross-platform date formatting (GNU first, BSD fallback)
- Remove unused all_template_repos dead code block
- Add CHANGELOG entry for Releases column in main report table

* fix: replace unsafe shell interpolation example with safe patterns

Use env: variable and action with: input instead of direct ${{ }}
interpolation in run: blocks to prevent shell injection from
PR-derived content (titles, labels, author names).

* fix: remove no-op shift statements and add trailing newline to action.yml

* feat: gate debug output behind --debug flag

- Add --debug CLI flag and debug action input (default: false)
- Add debug() function that only prints when DEBUG_MODE=true
- Replace all 26 'echo DEBUG:' calls with debug() function
- Update README, action.yml, and CHANGELOG

* fix: address set -e API call safety, date formatting, and docs accuracy

- Restructure all api_call assignments to if-guard pattern so set -e
  doesn't abort the script on API failures (both org and external repos)
- Use non-zero-padded day format in releases table (%-d GNU, %e BSD)
- Fix comment saying '> 1' to match format_metric() behavior of '> 0'
- Soften docs wording from 'all merged PRs' to 'merged PRs'
- Document 100-item-per-page API limit in comment template docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants