Related with #416

I'll follow this issue and #416 because it would be a great improvement to this project.

I suggest also another idea, I also tried this tool, it serves the same purpose as yours but it uses a different approach to generate changelog entries.

If a generic concept of entry provider is added to this tool to abstract the differences between Github/Gitlab/Bitbucket it would be great to also have a sort of LocalEntryProvider class that parse changelog entries directly from git log using the regexp approach, i.e. something like

• fix: Some issue fixed => to bugfix section
• merge: Some issue fixed => to merged branches section

and so on. What do you think?

This issue has not been touched for quite some time.
Is this being worked on?

If not, would it be possible to add some detail as to what needs changing?
Any helpful pointers to relevant sections in the code could speed up things.

EDIT: Is it "as simple" as adding a new fetcher?

This feature is ready in #657
Looks great. I want to double-check this code and then merge it.

In case if you don't want to wait:
I made separate repo to test GitLab things: https://github.com/github-changelog-generator/gitlab-changelog-generator

I can add you as owners there, so we can even make a separate gem for GitLab for now.

p.s. hmm. looks that we have to rename this project after this merge 😉 ***-changelog-generator

@skywinder an alternative to renaming the project would be to extract the common code in a changelog-generator project and have both the github and gitlab one depend on it?

Exactly. that's what I'm going to do soon.

What is the status of this?

@martijnsenden hi, it's a frozen. 🥶
but the good news, that this feature is already implemented. ✅
🙌 I need help with supporting this project.

It's been almost 4 years. Is GitLab support on the roadmap?