• Product Blogs
    • Français
    • 日本語
    • 한국어
    • Türkçe
    • Deutsch
    • Português do Brasil
    • Русский
    • Español
    • 简体中文
    • IDEs

      • AppCode
      • CLion
      • DataGrip
      • DataSpell
      • Fleet
      • GoLand
      • IntelliJ IDEA
      • MPS
      • PhpStorm
      • PyCharm
      • Rider
      • RubyMine
      • WebStorm
      • Toolbox App
    • Plugins

      • Big Data Tools
      • Quality Assurance
      • Rust
      • Scala
    • Team Tools

      • Code With Me
      • Datalore
      • Space
      • TeamCity
      • Upsource
      • YouTrack
      • Hub
      • Qodana
    • .NET & Visual Studio

      • .NET Tools
      • ReSharper C++
    • Languages

      • Kotlin
      • Ktor
    • Education

      • Edu Products
    • Company

      • News
      • Security
      • Team
      • JetBrains Platform
Space logo

The Space Blog

An all-in-one solution for software projects and teams

  • News
  • Software Development
  • Project Management
  • Team Collaboration
  • Extensibility
  • Webinars
Try for free

merge request

Webinar Recording: IntelliJ IDEA + Space = Complete Environment for Collaborative Development

Watch the recording of our latest webinar “IntelliJ IDEA + Space = Complete Environment for Collaborative Software Development”.

Valerie Andrianova Valerie Andrianova

Quality Gates in Merge Requests

Quality gates are a quality control technique used in collaborative software development. Though it’s quite a broad term, Space currently uses it only for merge request workflows. Simply put, a quality gate is a set of conditions that needs to be met before you can merge your commit into a protected branch (for example, the master). Let’s take a look at them in more detail. Types of quality gates

Alexey Totin Alexey Totin

Introducing Turn-based Code Reviews in Space

Today, we want to introduce you to the concept of turn-based code reviews in Space! The idea behind turn-based code reviews is to make the process of reviewing code as clear as possible for the author of the code, and the reviewers. When the Space team was looking at the typical code review process, we found two issues that could be improved: Who should take action? It's not always cle

Valerie Andrianova Valerie Andrianova
  • Privacy & Security
  • Terms of Use
  • Legal
  • Genuine tools
  • Français
  • 日本語
  • 한국어
  • Türkçe
  • Deutsch
  • Português do Brasil
  • Русский
  • Español
  • 简体中文
Copyright © 2000–2022 JetBrains s.r.o.