Add CHANGELOG.md + biweekly changelog-rollup workflow - #84
Open
xdotli wants to merge 1 commit into
Open
Conversation
Introduces a changelog for the list itself: CHANGELOG.md (Keep a Changelog-style, dated sections) seeded with the last two merge batches, plus .github/workflows/changelog.yml which opens a PR every ~two weeks rolling up merged PRs since the last entry. Mechanical only (gh pr list + keyword classification), no model calls; never pushes to main or merges itself, same as the daily scan.
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
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.
Adds a changelog for the list itself:
CHANGELOG.md(Keep a Changelog-style, dated sections), seeded with the last two merge batches (2026-07-30, 2026-08-20) so the format has real history from day one..github/workflows/changelog.yml: runs ~biweekly (1st/15th of month), readsgh pr list --state mergedsince the last dated CHANGELOG entry, classifies by title keyword (Added/Changed/Fixed/Removed), and opens a PR inserting the new section. Purely mechanical — no model calls, never pushes to main or merges itself, matches the daily scan's human-approves-every-PR invariant.Reviewed manually before opening — not self-merging per repo convention.