feat: enable tag_filter_pattern in config options

[trim21]

What does this do / why do we need it?

enable tag-filter-pattern in config options

What should your reviewer look out for in this PR?

if options in config file works and can be overwrited by args

Check lists

• Test passed
• Coding style (indentation, etc)

Which issue(s) does this PR fix?

close #70

[coveralls]

Pull Request Test Coverage Report for Build 159

• 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 75.207%

---

Totals
Change from base Build 155:	0.02%
Covered Lines:	1632
Relevant Lines:	2170

---

💛 - Coveralls

[rohitchawla22]

@trim21 Can we merge this PR in?
We are trying to achieve something similar where we want to generate changelogs separately for versions 2.* and a different one for versions 1.*
As both the versions of our application currently live in the same repository, git-chglog is not able to differentiate between two different versions.
Thanks

[trim21]

It's ready to be merged

[mithuns]

Whats blocking this, I think this is a great feature.

[trim21]

@mithuns I guess it's just because nobody is merging pr

[mithuns]

Why is the travis-ci not running ? I think that is a required check.

[estahn]

Any update on this? I guess this will also help with monorepos?

[trim21]

test on Travis has passed https://travis-ci.org/github/git-chglog/git-chglog/builds/676948779

[mavogel]

Thanks @trim21 ! We gonna fix the ci and release process separately and most probably move to gh-actions in #58. I gonna overrule the failed travis check, which succeeded as mentioned on the link above