hledgerorg
- 5 skills
- 0 followers
- 17 hours ago last updated
- ▌ Credits · hledgerorgUpdate the commit-authors table in doc/CREDITS.md from the latest git history. Run `just authors`, merge the new counts into the table, refresh notes for authors whose commit count grew significantly, and move them into the correct digit-section. Use for the periodic (e.g. year-end) CREDITS refresh.
- ▌ Release · hledgerorgDrive an hledger release (major, bugfix, or preview) using doc/RELEASING.md's "Release script" as the step list. Use in the hledger repo when the user says "let's do the X.Y.Z release" or similar.
- ▌ Changelogs · hledgerorgUpdate hledger's changelogs (*/CHANGES.md, one per package plus the project one in doc/). Run `just changelogs` to draft entries from git log since the last recorded commit, then polish them in phases (cleanup, wording, finalise). Use when asked to draft, update, polish or finalise changelogs.
- ▌ Binary Badges · hledgerorgCheck and refresh the version badges under "Packaged binaries" in site/src/install.md — update stale version numbers and set badge colour (green if current, red if outdated) by checking each package's actual page. Use when asked to update packaged/distro versions, refresh install.md badges, or similar.
- ▌ Regen Shelltests · hledgerorgRegenerate expected output in failing shelltestrunner v3 fixtures (`hledger/test/**/*.test`) after a hledger output-format change (alignment, column shifts, rendering tweaks). Use when many `.test` fixtures are stale because of a deliberate, audited rendering change.