#FLOW DIAGRAM FOR FREE#
#FLOW DIAGRAM HOW TO#
#FLOW DIAGRAM ANDROID#
#FLOW DIAGRAM CODE#

#FLOW DIAGRAM CODE#

With turn-based code reviews, Space makes it easy for both the author and the reviewer to understand whose turn it is to take action.

They can add comments and suggestions, or they can simply approve the request. Now you wait for your colleagues to review the changes. Later, you and your colleagues will have the option to select a code owner to review your changes as a part of quality gates. In your repository, you can create a special file named CODEOWNERS that specifies who is responsible for specific folders and files. Space will require a review based on code ownership Apart from code reviewer’s approval, you can set up a Space Automation job and a TeamCity check as gates. Quality gates are a mandatory and customizable set of conditions that need to be fulfilled before merging. The quality gates configured in Space require at least one person to review these changes. You can create a title and description for your merge request and see the commits that will be part of it. You can do this from within your IDE using the native integration, or you can find your branch in Space and create a merge request from there. Create a merge requestĬreate a merge request to begin the process of moving your new code into main. From your IDE, you can make changes, add a commit message, and then push this branch back to Space. With the Space Git flow, you make changes in a separate feature branch and then request a code review before merging it back to main. To start working on a new feature, you’ll need to either clone the repository to your machine, or use remote development with the IDE hosted on a virtual machine in the Space cloud. Once you’ve set up branch protection, the only way a change can make it to main is through a merge request. Watch this 3-minute video to see how the combination of the Space Git flow and TeamCity works in a project:

#FLOW DIAGRAM HOW TO#

How to Use the Space Git Flow With TeamCity Read this article to learn more about the Space Git flow.

#FLOW DIAGRAM ANDROID#

Introduce a code review process your team will love, integrated with IntelliJ IDEA and available on the go with Space iOS and Android apps.Achieve higher-quality code and a stable main branch by configuring quality gates based on TeamCity build status for merge requests.Using the Space Git flow integrated with TeamCity allows you to: Getting started with the Space Git flow is easy and doesn’t require going all-in, as you can mirror your existing Git repository without having to migrate, and you can switch back any time. The Space Git flow is a branching strategy that is similar to GitHub flow, but with a greater emphasis on safety when introducing changes to the main branch and the ability to scale to large projects and teams.

#FLOW DIAGRAM FOR FREE#

Get started with Space for free What Is the Space Git Flow, and Why Use it? In this blog post, we’ll introduce the combo of the Space Git flow and TeamCity, and guide you through the process of using it in your project. The native integration between tools will save you time and effort by ensuring you have a complete and well-integrated flow with a unified UI.Īdopting the Space Git flow with TeamCity is easy and allows you to keep your main branch stable while controlling changes automatically. Space provides you with Git hosting, code reviews, and quality gates, while TeamCity offers a build pipeline. The powerful combination of JetBrains Space Git flow with TeamCity offers a complete solution to help you achieve better code quality and keep your main branch green with stable builds. Do you use feature branches or Git flow to ensure code quality?

Flow diagram