JetBrains Space Help

Code Tips

Using Space to work on source code in Git repositories? These tips will help you gain more productivity.

Chat about code

Ask questions and discuss code in Git repositories.

Space makes it easy for you and your team to review code, discuss changes, and keep track of accumulated knowledge.

Have a question or want to discuss? Ask it inline! Mention your team or specific colleagues, so they get a chat notification.

Those involved can navigate to the code and discuss inline if they ant to, or simply respond from within their chat.

More about reviewing code in Space...

Code Reviews in your IDE

Use any IntelliJ IDEA-based IDE to browse code reviews, submit comments, and accept changes. Review code where you write it: in the IDE!

After making a change, you can request a code review from one or more team members.

Code reviews and merge requests can be accessed from your browser, using the Space desktop application, and from within the IDE!

The Space plugin is bundled in IntelliJ IDEA, and you can install the Space plugin manually in our other IDEs.

Use the plugin to:

The IDE shows basic details of the code review, such as who the authors and reviewers are. You can checkout the code review's branch, and use the code review timeline to see all comments and changes that were made during the lifetime of a code review.

You can write additional comments on the code review, and browse and respond to threads as well. Without having to leave the IDE!

More about the Space Plugin for IntelliJ-based IDEs...

Turn-based Code Reviews

Who should take action? 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 clear whether the ball is in the court of the author or that of one of the reviewers.

It is not uncommon for a reviewer to write: "Could you please explain the meaning of this part?", and then delete their comment once they've found the answer to their question further in the code. Does it make sense to send comments immediately during a review, bothering the author and reviewers with what could be temporary remarks? Can comments be buffered as drafts?

The turn-based code review process in Space provides an answer to both questions. Status indicators for each of the participants reflect whose turn it is at any moment. Code review comments are added as drafts, and sent in one go when someone's turn in the review ends.

More about code reviews in Space...

Mark a message as resolvable in Code Review

Draw attention to something that requires action when reviewing code. Flag a message in Code Review for follow-up.

flag-message-code-reviews

You can mark messages in the Code Review Timeline with a Resolved/ Unresolved status.

This feature is useful for drawing attention to something that requires action. Space will not let you close the code review until all issues are resolved.

Go to a Code Review, make sure you're on the Timeline tab, and do one of the following:

  • To mark a message unresolved, hover over the message and click on the ! icon.

  • To mark a message resolved, click on Resolve above the message.

You can also unflag a discussion by using the ! icon again.

More about code reviews in Space...

Last modified: 25 June 2021