Last week we focused mostly on bug fixes and improvements in response to your requests. As always we're waiting for your feedback and suggestions on firstname.lastname@example.org.
Here at Buddy we’ve been working together for over 7 years. We’ve done many projects of different size and type, continually evolving and improving the way we collaborate. Upon hearing ‘collaborate’ we usually think of words like manager, milestone, sprint, scrum or kanban. In this article we shall focus on stuff related with code collaboration: introducing changes, solving conflicts, using branches, and more.
Today’s update brings a nice saucerful of goodies with recurrent pipelines and commit commands as the main course. In other words, you can now schedule your executions to run on intervals as well as trigger them manually with commit commands.
As a software development company we know well that the very basis of this business are developers, whose skill and knowledge create the most valuable asset in the industry: code.
March has landed, and with it another package of features and improvements. As you can see, we’ve launched a blog to help you get the most of Buddy as well as inform you of updates and new features. If you'd like to submit a use case or publish a guest post, go ahead and shoot me an email at email@example.com.
Here’s the list of features and improvements that we delivered in Buddy in the last four weeks. As always, we’re looking forward to your feedback, use cases and requests in the comment section and at firstname.lastname@example.org.
This article summarizes the most important changes introduced to the service between November 2015 and January 2016. Alongside tons of bugfixes and numerous improvements to the UI, it represents the way that Buddy passed since it officially launched and changed its name from Meat! to Buddy.