Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions .changeset/commit-helper-passthrough.md

This file was deleted.

10 changes: 10 additions & 0 deletions packages/commit-helper/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# @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](https://marketplace.atlassian.com/apps/1217129), 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.

## 1.2.2

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/commit-helper/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@naverpay/commit-helper",
"version": "1.2.2",
"version": "2.0.0",
"description": "help your commit in git",
"main": "./dist/index.js",
"repository": {
Expand Down
Loading