We’ve been getting more feedback about managing your files directly in Beanstalk. One key feature missing from our new file management tools was the ability to rename files. Today we’re proud to announce that you can do just that in your Beanstalk account.
Renaming a file is simple. When viewing a file, click on the filename and it will bring up the rename form.
Type your new filename and click “Rename” button.
After the form submits, you’ll be redirected to the file page with its new name. A commit is created in real-time so your team will be able to pull these changes immediately.
For our customers with really complex code review processes, Review Board (and their hosted solution RBCommons) has built an integration with Beanstalk. You can now tie your commits with a code review process in Review Board.
And because their team is so generous, they’ve offered Beanstalk customers 20% off the first 3 months. If you’re interested, just sign up and mention Beanstalk in the referral link.
While we’re on the topic of code review: how do you perform code reviews with your team? Share with us below, or email me. I’d love to talk about it.
We recently announced our new file editor in Beanstalk. Since then, we’ve been getting a lot of great responses about this welcomed feature. Users who never used Git or Subversion can now make changes to their project and deploy them with ease, all within the browser.
Today, we’re updating our File Node API with create, update, and delete support. This update will allow third-party developers to take advantage of Beanstalk’s new file editing operations in their apps. Just like the web, these operations are processed in real-time and available to everyone to fetch immediately.
Ever found yourself in a situation where you need to find every commit associated with a specific file? Today we added a new feature just for that. It’s called File History and you can find it on every file page in the Browse section of your repository.
Today we continue a series of improvements to make your life with Git easier and more comfortable.
The biggest advantage of Git for most people is the power and convenience of it’s branching mechanism. With Git, it’s sometimes just too hard to resist creating a new branch to work on a feature that popped into your head, in the middle of working on something else. And that’s okay, because you can’t bottle up inspiration. Naturally, after a while, you end up with quite a few branches in your repository!
However, now that you have all these branches, there has to be a better way of managing them – discovering, comparing, merging branches becomes a chore. Today, we’re making all of this much easier with our brand new Branches page:
Beanstalk has focused on private teams since day one. Our goal is to make your team more productive and efficient by giving you tools to decrease friction inside your development process and improve collaboration.
Sometimes that means giving you a tool that ships the latest version of your site to a cluster of 40 production servers with a single click. Sometimes it means getting out of your way and provide the fastest possible connection to source code for your developers around the globe with Git CDN (now in beta). Today we’ve released a feature that will make the process of managing user permissions a whole different story.
Beanstalk allows designers and developers to store source code, track changes, and collaborate with team.