Add extract-git-issues utility for release issue collection#177
Open
smorrisods wants to merge 3 commits intodevelopfrom
Open
Add extract-git-issues utility for release issue collection#177smorrisods wants to merge 3 commits intodevelopfrom
smorrisods wants to merge 3 commits intodevelopfrom
Conversation
smorrisods
commented
Feb 19, 2026
Collaborator
Author
smorrisods
left a comment
smorrisods
left a comment
There was a problem hiding this comment.
Thanks for the review, @MeaghanCarrieres! Here's some responses.
- Add scripts/extract-git-issues.js to extract Jira issue keys from commit subjects after a release tag. - Support plain output, Markdown-friendly issue links, and optional JSON output. - Add optional Jira enrichment for issue titles using REST API credentials from CLI flags or environment variables. - Default mode reads commit subjects from tag..HEAD. - Optional --date mode uses the tag timestamp as a git log --since boundary. - Optional normalisation controls include --no-unique and --no-sort. - Optional --projectKey constrains matching to a single Jira project key. - Use execFile for git invocations to avoid shell interpolation of user-supplied tag values. - Keep failures visible with explicit error output and non-zero exit code on fatal errors. - Document script usage and options in scripts/README.md. - Add dotenv dependency and lockfile updates to support environment- based configuration.
Node version declarations were split across `.nvmrc`, `.npmrc`, and workflow inputs. That made drift likely and CI/local behaviour less predictable. - Updated reusable GitHub workflows to use `actions/setup-node@v4` with `node-version-file: '.nvmrc'`. - Removed `node-version` input plumbing from reusable workflows and from workflow callers in `main.yml`. - Aligned `.npmrc` `node-version` with `.nvmrc` (`22.22.0`). - Added root `package.json` `engines` for Node and pnpm ranges. - Updated internal setup docs to reference authoritative version files instead of hardcoded standalone values. - Establishes one authoritative Node version for local and CI behaviour. - Reduces maintenance overhead and version skew during upgrades. - Makes Node/pnpm expectations explicit for contributors and tooling. - No runtime code paths changed in this commit.
## Context Tool versions were discoverable in files, but not obvious from the top of the main README. ## What Changed - Added badges for: - Node (`.nvmrc` target) - pnpm (`packageManager`) - Stencil (`@stencil/core` in core component library) - TypeScript (`typescript` dev dependency in core component library) - Added a short line documenting that repo-root files are authoritative for toolchain versions. ## Why - Improves contributor onboarding by surfacing key versions immediately. - Reduces guesswork when setting up local development environments. - Keeps version communication close to where contributors start. ## Notes - Badge label for TypeScript intentionally uses `typescipt` per request.
smorrisods
force-pushed
the
scott/task/add-git-issue-extractor-script
branch
from
e2a089c to
0c9407c
Compare
MeaghanCarrieres
approved these changes
Mar 4, 2026
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
2 participants
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.
Summary
This PR adds a new script to extract Jira issue keys from git commit subjects since a specified release tag.
What’s included
scripts/extract-git-issues.jsscripts/README.mddotenvdependency updates in:package.jsonpnpm-lock.yamlBehaviour
--tag(required)--projectKeyfiltering--no-uniqueand--no-sort--datemode (uses tag timestamp withgit log --since)--jsonoutputNotes