@naverpay/commit-helper@2.0.0

Major Changes

• c0c01ef: Add passthrough for Jira/Linear-style issue keys, and make re-tagging match only your branch's own tag.

  passthrough — list your project keys, and branches that already contain the full key are tagged as-is. With { "passthrough": ["PROJ"] }, branch feature/PROJ-1871 becomes [PROJ-1871]. Only the keys you list are tagged, so unrelated text like UTF-8 is never mistaken for an issue. Key detection matches Jigit, so a branch links the same way in Jira and here.

  Breaking change — commit-helper skips a commit that is already tagged, and what counts as "already tagged" changed. Before, any [#…] tag in the message stopped it. Now, only your current branch's own tag does. For example, on branch feature/123, a message you wrote as [#999] fix used to be left alone, but now becomes [#123] [#999] fix. Re-running the hook or git commit --amend still never adds your tag twice — this now includes verbatim keys like [PROJ-1871], which the old check could not detect.

@naverpay/commithelper-go@1.4.0

Minor Changes

• bea4bcc: Add passthrough for verbatim Jira/Linear-style issue keys, plus two tagging fixes and a bundled JSON schema.

  • passthrough. List the project keys to recognize (e.g. "passthrough": ["PROJ", "OPS"]); a branch like feature/PROJ-1871 is tagged [PROJ-1871]. Key recognition matches Jigit (<KEY>-<1–7 digit number>, found anywhere in the branch), so a listed project links identically in commithelper and Jigit. Only listed projects are tagged, so unrelated UPPERCASE-NUMBER tokens (e.g. UTF-8) are not mistaken for issues. rules (GitHub prefixes) take precedence when a branch matches both.
  • Idempotent re-tagging. A message is left unchanged when the branch's reference is already present as a whole token, so git commit --amend and hook re-runs never stack tags — including template tags placed in the message body.
  • Protected branches are evaluated before the already-tagged check, so a pre-tagged message cannot bypass protect.
  • schema.json is bundled in the package; reference it via "$schema": "./node_modules/@naverpay/commithelper-go/schema.json" for editor autocompletion and validation (works offline, no CDN).

@naverpay/commithelper-go-win32-x64@1.4.0

@naverpay/commithelper-go-win32-x64@1.4.0

@naverpay/commithelper-go-linux-x64@1.4.0

@naverpay/commithelper-go-linux-x64@1.4.0

@naverpay/commithelper-go-darwin-x64@1.4.0

@naverpay/commithelper-go-darwin-x64@1.4.0

@naverpay/commithelper-go-darwin-arm64@1.4.0

@naverpay/commithelper-go-darwin-arm64@1.4.0

@naverpay/commithelper-go@1.4.0-canary.260701-bea4bcc

🚧 Pre-release

This release is a pre-release version of @naverpay/commithelper-go.
Please make sure to thoroughly test it before deploying to production.

Changes

• ✨ feat: add passthrough for verbatim issue keys
• ♻️ refactor: match Jigit for passthrough key recognition

@naverpay/commithelper-go-win32-x64@1.4.0-canary.260701-bea4bcc

🚧 Pre-release

This release is a pre-release version of @naverpay/commithelper-go-win32-x64.
Please make sure to thoroughly test it before deploying to production.

Changes

@naverpay/commithelper-go-linux-x64@1.4.0-canary.260701-bea4bcc

🚧 Pre-release

This release is a pre-release version of @naverpay/commithelper-go-linux-x64.
Please make sure to thoroughly test it before deploying to production.

Changes

@naverpay/commithelper-go-darwin-x64@1.4.0-canary.260701-bea4bcc

🚧 Pre-release

This release is a pre-release version of @naverpay/commithelper-go-darwin-x64.
Please make sure to thoroughly test it before deploying to production.

Changes