$ show Songmu/tagpr
tagpr is a Go CLI tool that automates the GitHub release workflow. It runs as a GitHub Action, monitoring the main branch. When unreleased changes exist, it creates or updates a release pull request with an auto-generated changelog. When that PR is merged, tagpr automatically tags the merge commit with the next semantic or calendar version and creates a GitHub Release. It supports monorepo configurations via tag prefixes, custom version files, label-based version bumping, and both SemVer and CalVer schemes. The tool integrates deeply with the GitHub API (PRs, releases, git trees, issues) and local git commands. It also includes a reusable submodule `gh2changelog` for generating changelogs from GitHub release notes. The codebase is well-structured, with clear separation of concerns, extensive tests, and a functional options pattern for configuration.
The LLM identified 3 files worth highlighting for reuse:
Encapsulates version handling for both semantic versioning and calendar versioning. Provides methods for parsing, formatting (Naked/Tag), guessing the next version from labels, and computing the next CalVer version based on current time. The `semv` struct is self-contained and could be extracted into a standalone library for any Go project needing version management.
Implements automatic detection of version files in a repository by walking the directory tree and matching version patterns. Supports multiple language-specific files (gemspec, Go, Python, Node, Perl, Rust, etc.). Also provides functions to bump the version in a file and retrieve the version from a file. The detection logic is reusable for any tool that needs to locate and update version strings in source files.
A standalone Go library (separate go.mod) for generating changelogs from GitHub release notes. It uses the GitHub API's GenerateReleaseNotes endpoint and converts the output to Keep a Changelog format. Supports tag prefixes for monorepos, custom release YAML paths, and major version filtering. The library is used by tagpr but can be imported independently for any project needing changelog automation.