ChangeHub delivers the information you need without interrupting developers. We make this happen by integrating directly with your codebase and turning your repository into a living changelog.
Hi Hunters!
I'm Bram and I'm one of the creators of ChangeHub. Thanks @vinch for hunting us!
ChangeHub started during a company retreat in 2014 as a proof of concept to make it easier for our product managers and clients to know what changes our engineers were making on a daily basis. We've been using it as an internal tool ever since.
It works by connecting your repository (hosted on GitHub or GitLab) and have your engineers write changelogs (using the https://keepachangelog.com/en/1.... format) in their pull requests. We use these to display an overview of the changes that have been made and giving you an easy reference to communicate about these to your customers.
The last couple of months we've been making several changes to allow other teams to use ChangeHub. We've documented this process on our blog: https://madewithlove.com/communi...
You can also have a look at our public changelog: https://app.changehub.io/share/p...
Hi Bram - happy to help! Essentially i go to the create project page where i could see my repo i'd added previously, but clicking 'Setup project' did nothing, in the network panel it was returning a 404. I hope that helps.
This looks very interesting! But what I don't understand: Where do I find my genrated changelog? Does ChangeHub offer a Dashboard? Or will it be CHANGELOG.md file in the repository?
@mr_svzi For each project you create in ChangeHub you'll have access to a dashboard that lists the published releases and their changelogs, as well as a list of upcoming changes (shown in https://share.getcloudapp.com/7K...). We currently don't generate a CHANGELOG.md file in the repository itself.
@mr_svzi The changelog is available inside ChangeHub and can be shared publicly. As an example, here is the public changelog of ChangeHub: https://app.changehub.io/share/p...
@mr_svzi We're mainly focussed on aggregating the changelogs and providing an in-app overview that you can use as input for other channels (such as Beamer/Headway/Your website/...). We do plan on exploring how ChangeHub can make this workflow easier and an API could be one of the solutions.
@gertjanwilde We currently don't offer embed widgets. Our initial goal was aggregating the changelogs so that you could use this (raw) input with products such as Headway/Beamer.
If you're currently using any of those products I'd be interested to hear your thoughts on how you currently gather the input to write changelogs and if ChangeHub can help with that.
There's a lot I like about this product. The design, the simplicity and the clear statement of what it does. Never heard of https://keepachangelog.com/en/1.... before which I think is a good specification on how changelogs should look like. I think one downside is that you have to maintain the changelog file manually. I just wonder who is going to do this? The developer? The product owner/manager? And when is the time to mark a new version? If all this is clear, then ChangeHub seems to be a great way to visualize this information. Great job!
@sarensw Thanks for the kind words.
Our aim is to have developers that fix bugs or introduce new features to be the ones that write the changelog and include it in the pull request description because they are the ones closest to the actual changes that are being made. This does require a lot of discipline and writing skills to be able to phrase a message that someone less technical is able to understand.
We currently consider creating (and publishing) a tag in your git repository to be a release. We realize that this is a very specific workflow and not everyone makes use of git tags so we're also in the process of exploring other workflows.
@bramdevries I get your point. I think it really depends on the maturity of the product. At a certain level, you most likely would have a product manager/owner who would like to control what is shown in the change-log. We have the same challenge in our product where a developer is supposed to use feature flags as part of their development workflow. So flags are in JSON and committed together with changes to allow for trunk-based development. But at a certain maturity of the product, a product manager/owner would like to configure the flags using a UI for the customer maybe. So delivering the message on what the product is about is key I think. And also a big challenge ;). I'm interested to see how your product tackles this challenge.
p/general
p/ama
p/introduce-yourself
p/self-promotion
p/producthunt
p/kraftful
p/wisprflow
p/screaming-frog-seo-spider
p/xnapper
p/google-chrome
p/fine
p/openai-api
p/bolt-new
p/elevenlabs
p/notion
p/attio
Replies
ChangeHub
ChangeHub
ChangeHub
ChangeHub
SaaS Blocks by Apideck
ChangeHub
SaaS Blocks by Apideck
ChangeHub
Servebolt
ChangeHub
ChangeHub
ChangeHub