2021-07-30
1710
#node
Indermohan Singh
61102
Jul 30, 2021 ⋅ 6 min read

Automatically generate and release a changelog using Node.js

Indermohan Singh JavaScript developer interested in Angular, RxJS, and Ionic framework.

Recent posts:

What happens when dev communities die Stack Overflow’s slow collapse

What happens when dev communities die: Stack Overflow’s slow collapse

Explore how Stack Overflow’s slow collapse affects programming and the possible future for Stack Overflow vs. generative AI competition.

Shalitha Suranga
Aug 29, 2025 ⋅ 10 min read
How to build a multimodal AI app with voice and vision in Next.js

How to build a multimodal AI app with voice and vision in Next.js

Learn how to build multimodal AI interactions to process images, audio, and even real-time video streams, using Next.js and Gemini.

Elijah Asaolu
Aug 29, 2025 ⋅ 6 min read
i tried kiro and here is what i learned

I tried out Kiro: Here’s what I learned

Check out Kiro, AWS’s AI-powered IDE, see what makes it different from other AI coding tools, and explore whether it lives up to the hype.

Elijah Asaolu
Aug 28, 2025 ⋅ 5 min read
Go Design Pattern Article Image With Logo

Why Go design patterns still matter

Here’s how three design patterns solved our Go microservices scaling problems without sacrificing simplicity.

Peter Aideloje
Aug 28, 2025 ⋅ 2 min read
View all posts

4 Replies to "Automatically generate and release a changelog using Node.js"

  1. Often our team will make commits on each feature or developer branch, sometimes these may be work in progress changes. Such as committing work at the end of the day even though it isn’t feature complete or other various reasons. How does this workflow fit in with partially feature complete commits? It doesn’t make sense to follow this for every commit when all that matters to us is the squashed commit for release. Can this workflow only be applied to named branches? Would love to see and edit or follow-up on this related area.

    1. Thanks Ash. That’s a good question.

      1. You can always use a commit message which has the conventional commit structure but doesn’t have details. E.g: “type: WIP”. Here type can be feat, fix, chore and so on.

      2. Before you merge the feature branch then you clean the commit messages and merge.
      3. From there on, it’s like mentioned in the article.

      I hope it helps. I’d be interested in writing a follow up article.

      Thanks.

Leave a Reply