Statistics: add GitHub Actions workflow - #4295
Draft
ddbeck wants to merge 2 commits into
Draft
Conversation
This is probably only going to ever run in GitHub Actions workflows, so this doesn't need to be terribly ergonomic, but if you want to try it, run: npm run --silent stats -- | npx tsx ./scripts/stats-report.ts -
ddbeck
force-pushed
the
statistics-add-github-actions-workflow-for-produ/vxuyrykmprkx
branch
from
September 2, 2026 16:00
310ce55 to
f019631
Compare
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.
This adds a GitHub Actions workflow that posts a comment with the results of
stats-report.tsto a designated issue based on a nominated pair of commits. By itself, this won't be terribly useful. In a follow up PR, I'll extend this to post on a schedule, like I previously did manually in #788.It's GitHub Actions, so this is tough to review. Mostly, I suggest looking at the
runsteps to make sure I'm not doing anything confusing or destructive. I imagine "add a comment to explain this" as the most likely thing you'll find here.If you really want to test this, you can push this branch to your own fork, then run a command like:
Or you could just trust me that I've done this a dozen times myself. 😓
Depends on #4294.
Towards #3510.