Coming Soon: Release & Change Sensors
The next release of Hiphops is almost ready to be shipped, and it's a big one. In fact, it's our very first release without the beta designation 🎉. Whilst we're still putting the finishing touches on everything, we'd like to start giving you a taste of what's to come.
Watching teams use Hiphops in the wild and process millions of changes through our system has been incredible. We're currently processing and analysing around 80,000 events from our user's repositories per day, which is huge when you consider this is just our closed beta cohort. This release takes everything we've learned in the beta and refines it into a solid end-to-end experience for tech teams and their stakeholders. We couldn't have built this without our beta customers, so a huge shout out to them 🙌.
The two most important concepts being introduced in Hiphops v1.0 are change sensors and release sensors.
What do they do?
As you might imagine from the name, these configurable resources have the job of detecting changes and releases in your repositories. Using a few lines of YAML config, users can set up rules to filter and match their repository events and map them to either releases or changes within Hiphops itself. This is powerful. It means teams can see where every change is in their process at all times across all repositories. Searching historic changes by keyword, author and pretty much any other data point is trivial.
However, it's not just about visibility. Sensors also allow you to perform quick automations, usually in just two lines of code. Currently our automations cover automatic approval/rejection of changes, auto labelling (both ML driven and custom), and GitHub release creation.
In addition the two sensors inherently automate various tasks just by matching an event. A release sensor will always attempt to automatically gather readable release notes for you, just as a change sensor will automatically categorise a change and analyse its health.
We call these automations on sensors 'actions' (yes, it's a very original name). More actions are coming in the very near future, including the ability to trigger GitHub workflows, gather approvals, and call your own custom webhooks.
Works out of the box 🎁
One of our guiding principles when building Hiphops is that it should be useful in a few clicks. As such every project has a default change sensor that will analyse and track all changes in your code without performing any other actions. This means you get rich data on your dev process immediately without any extra effort, and can start to understand what custom config you will actually need.
In the near future we'll be adding historical analysis, where we back load all your historical changes before installing Hiphops, run them through our analysis and present you the results. This means you can install Hiphops and immediately begin to dive into your data and gain insights.
I hope you're as excited to use Hiphops as we are to share it with you. If you'd like to be notified when v1.0 lands, sign up to our waitlist to request access.