How to protect code with Buddy and GitHub status checks

In this guide, we’ll show you how to secure yourself from merging errors in your GitHub projects with help of BuddyWorks testing features.

Introduction

Git and its branches are one of the best inventions since sliced bread (well, at least for developers). Employing branches, gitflow and pull requests to development workflow is a great way to ensure code quality.

In short, Gitflow is a type of workflow in which all new features and bug fixes are made on dedicated branches; only when the branch is tested it can be merged to the master branch.

Make sure to check out our insight article on 5 types of Git workflows.

Gitflow in practice may look like this:

1. Junior Developer receives a task ‘develop a new feature’
2. They create a new branch and codes the feature
3. When the feature is ready, the developer creates a pull request
4. Senior Developer reviews the code and assigns back comments
5. Finally, the feature branch is merged into the master branch and the new feature is ready for deployment

However, no matter how experienced and thorough the Senior Dev is (the coffee wears off, eventually!), such…