First time at Zeet?

10 Apr
min read

Flexibility To Your Git-based Projects With Branch Changes

With git branch locking and multiple Zeet Branch to git branch mappings, you can now have more control over your deployments.

Jack Dwyer


Share this article

Fine-Grained Access Control for Your Kubernetes Environments

Branch management just got a huge upgrade with some new changes.

There are two key components to Branch Changes:

  1. Locking Zeet Branches to Git Commits - You can now lock a Zeet branch to a specific git commit instead of just a git branch. This enables precise reproducibility and environment locking. No more surprises from a branch moving under you unexpectedly.
  1. Multiple Zeet Branches per git branch

With Branch Changes, you can spin up multiple Zeet branches from the same git branch. For example, you could have a "staging" and "production" Zeet branch based on "main" with small config tweaks between them.

Combined, these two features enable flexible workflows like canary deployments, seamless hotfixes, and isolated testing. You get all the power of GitOps without the complexity.

Give it a shot, it's live right now!

Subscribe to Changelog newsletter

Jack from the Zeet team shares DevOps & SRE learnings, top articles, and new Zeet features in a twice-a-month newsletter.

Thank you!

Your submission has been processed
Oops! Something went wrong while submitting the form.