In the past few weeks, we’ve made a lot of improvements to Hutte. List views should load much faster now, and we’ve added a few UI informational elements that will speed up your workflow and give you more information about your projects. And that’s just the start!
Sandbox “History” tab now shows which Org it was refreshed from
We made a small upgrade to the Sandbox “History” tab. Now, next to each refresh, you’ll see a sentence that tells you which Org the Sandbox was refreshed from.
List view speed improvement
We’ve made substantial improvements to the loading speed of listviews in Scratch Orgs and Sandbox features. This is particularly beneficial for projects with a large volume of completed features and/or terminated Scratch Orgs.
Mitigated risk of overwriting when working in parallel on the same metadata
We’ve made an improvement to the Sandbox workflow in Hutte that fixes the rare overwriting issue of simultaneous changes, which could arise when two users were working on the same metadata in different Sandboxes in parallel.
👉
Previously, larger teams would sometimes encounter an issue where one team’s work could be overwritten when two or more different teams were working on new features involving the same metadata, especially when working in longer-living Developer Sandboxes. Such overwrites were visible on Git but could easily be missed in reviews.
Now, when you commit for the first time on a new Sandbox feature, the feature branch will branch out from the time that corresponds to the last refresh date of the Sandbox you’re using to develop the feature. This should eliminate the issue of overwriting other feature changes by accident.
Minor updates to the "Pull changes" form
We’ve upgraded the layout of the “Pull changes” form in Hutte. They’re mostly small things, such as removing the option to select a branch to branch out from after the first commit (since the branch has already been created by the first commit).
We also fixed some spacing and styling errors, and a couple of other things. You won’t notice most of these changes, but they’ll make using the “Pull changes” form just a tad smoother going forward.
Hide/show empty components when pulling changes
We’ve added a toggle to the “All components” tab that appears when you pull changes. It’s toggled “on” by default, and hides all empty component types from the list of components. Toggle it “off” if you want to see the empty component types in the list.
We’ve also added a refresh button as a permanent option inside each individual component section.
Branch name will no longer be overwritten when naming a new feature or Scratch Org
We made a minor fix to the workflow when making a new feature or Scratch Org in Hutte. Before, when a user would populate a branch name before naming a new feature or Scratch Org, the branch name would be overwritten when the user named the new feature/Scratch Org. This meant the user would have to go back and specify the correct branch a second time. We’ve now fixed this so that the branch name won’t be overwritten when this occurs.
Explore these improvements firsthand
☎️
Get in touch with us to discover how we can customize a superior user experience for you!
Harald is the Co-Founder of Hutte, bringing his vision of no-code DevOps to life. His passion enables teams and individuals to focus on what matters most – bringing value to the users they build for.
