Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Merge commit not ignore with ignore-commit-pattern "Merge.*" and --issue-pattern, --issue-url

See original GitHub issue

Im using this command npx auto-changelog --tag-prefix '' --issue-pattern "[A-Z]+-\d+" --issue-url 'https://xxx.atlassian.net/browse/{id}' --ignore-commit-pattern "^(Initial.*|Merge.*)"

The Merge pull request still exist, not ignored.

### Changelog

All notable changes to this project will be documented in this file. Dates are displayed in UTC.

Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).

#### [1.0.0-alpha3](https://github.com/ookangzheng/test-action-semantic-release/compare/1.0.0-alpha2...1.0.0-alpha3)

> 27 January 2021

- fix: SYG-121 bac [`#40`](https://github.com/ookangzheng/test-action-semantic-release/pull/40)
- Merge pull request #40 from ookangzheng/SYG-121 [`#SYG-121`](https://xxx.atlassian.net/browse/SYG-121) [`#SYG-121`](https://xxx.atlassian.net/browse/SYG-121)
- fix: SYG-121 bac [`#SYG-121`](https://xxx.atlassian.net/browse/SYG-121)

#### [1.0.0-alpha2](https://github.com/ookangzheng/test-action-semantic-release/compare/1.0.0-alpha1...1.0.0-alpha2)

> 27 January 2021

- fix: SYG-122 local.sh typo [`#39`](https://github.com/ookangzheng/test-action-semantic-release/pull/39)
- Merge pull request #39 from ookangzheng/SYG-122 [`#SYG-122`](https://xxx.atlassian.net/browse/SYG-122) [`#SYG-122`](https://xxx.atlassian.net/browse/SYG-122)
- fix: SYG-122 local.sh typo [`#SYG-122`](https://xxx.atlassian.net/browse/SYG-122)
- chore: UNRELEASE.md [`28a274c`](https://github.com/ookangzheng/test-action-semantic-release/commit/28a274c39607f13f00b6079aeada8726e64253b5)

#### [1.0.0-alpha1](https://github.com/ookangzheng/test-action-semantic-release/compare/1.0.0-alpha0...1.0.0-alpha1)

> 27 January 2021

- fix: SYG-123 typo [`#38`](https://github.com/ookangzheng/test-action-semantic-release/pull/38)
- Merge pull request #38 from ookangzheng/SYG-123 [`#SYG-123`](httx.ps://xxx.atlassian.net/browse/SYG-123) [`#SYG-123`](https://xxx.atlassian.net/browse/SYG-123)
- fix: SYG-123 typo [`#SYG-123`](https://xx.atlassian.net/browse/SYG-123)

#### 1.0.0-alpha0

> 27 January 2021

- fix: SYG-123 init repo [`#SYG-123`](https://xxx.atlassian.net/browse/SYG-123)

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:7 (2 by maintainers)

Top GitHub Comments

2reactions

cookpetecommented, May 21, 2021

Ah ok, in your case the bumps are merges, and being listed as merges in the changelog. --ignore-commit-pattern only applies to lists of commits (which appear below the lists of merges and fixes).

I guess it would make sense for --ignore-commit-pattern to apply to merge commits and fixes too? I’ll look into it.

2reactions

patrickp-at-workcommented, Mar 30, 2021

I can confirm this using v2.2.1

Top Results From Across the Web

How to avoid merge-commit hell on GitHub/BitBucket

Rebase Feature Branches Before Merging. If you want to avoid merge commits, you need to ensure all commits are fast-forwards. You do this...

git-merge Documentation - Git

Incorporates changes from the named commits (since the time their histories diverged from the current branch) into the current branch. This command is...

PhpStorm - Apply changes from one Git branch to another

Select the branch that you want to merge into the current branch, click Modify options and choose from the following: --no-ff : a...

Merge request pipelines - GitLab Docs

This option is only available when merge request pipelines are configured for the pipeline and the source branch has at least one commit....

Git Undo Merge – How to Revert the Last Merge Commit in Git

But what if you finish merging and realize you forgot to do one more thing? Or what if you accidentally merge when you...