Skip to content

Latest commit

 

History

History
116 lines (82 loc) · 6.19 KB

README.md

File metadata and controls

116 lines (82 loc) · 6.19 KB

GitLive Documentation

Development teams merge faster with GitLive

Video


GitLive helps you and your fellow contributors merge faster by avoiding conflicts and encouraging eager and continuous code review directly inside the IDE.


Do not let merge conflicts break your flow

Indicators in the gutter of your editor show the changes others are making. Computed from all active branches, the indicators update as you and your team code together. Get notified the moment you make a change that conflicts with another branch. Compare their changes to your own and cherry‑pick individual changes directly into your local files.

Merge Conflicts


Get the ultimate perspective on all work in progress

Perform eager and continuous code review directly in your IDE with the team view. See who is online, their active branches and changes in a single repository or across your organization, updated in real‑time. Get notified when you fall behind the main branch or your tracking branch. Inspect the changed files in the repository view to know if they will merge cleanly with your own local changes before you pull.

Team View


Let your team know what you are working on

Connect your issue tracker to see each other's current issue in the team view. The issue you are working on is determined by your current branch and updates automatically. View your current issue and select another issue to work on via the status bar. Switching issues will check out an existing feature branch or create a new one for you if needed.

Issue Tracker


Contents

  1. Installation
    1. Android Studio
    2. Other JetBrains IDE's
    3. VS Code
  2. Setting up GitLive
    1. As an Admin
      1. Android Studio
      2. Other JetBrains IDE's
      3. VS Code
    2. As a Team Member
      1. Android Studio
      2. Other JetBrains IDE's
      3. VS Code
  3. Account Management
    1. Android Studio
    2. Other JetBrains IDE's
    3. VS Code
  4. Visibility
    1. Android Studio
    2. Other JetBrains IDE's
    3. VS Code
    4. Privacy
      1. Android Studio
      2. Other JetBrains IDE's
      3. VS Code
  5. Video Calling
    1. Android Studio
    2. Other JetBrains IDE's
    3. VS Code

Contributing to GitLive

We're a tool built for developers, by developers. So your contributions are important to us! Please review this section to make the process of contributing as smooth and efficient as possible.

Reporting an Issue

GitLive uses Github Issue Tracking to track issues (mainly bugs). If you've found a bug, this is the place to start.

  1. You'll need to create a (free) GitHub account in order to submit an issue.
  2. Search the current issues to see if the bug has already been reported.
  3. If it hasn't, you can Open a new Issue.
    1. Please include as much information as possible - a title and a clear description at the very least.

Feature Requests

Feature requests are welcome. But please take a moment to find out whether your idea fits with the scope and aims of the project, and provide as much detail as you can.

Improving the Documentation

If there are any improvements you would like to see to our documentation, you can also use the Github issue tracking system. Our documentation is all open source, so if there are any improvements you would like to make yourself, you can do so via a pull request, which we will then review.

Serving your Changes Locally

Install the bundler if you don't have it already.

gem install bundler

Install the dependencies with Bundler:

bundle install

Run the following to serve the site locally:

bundle exec jekyll serve

Now you will be able to view your changes locally by going to:

http://localhost:4000

You can find more on Deployment Methods page on Jekyll website.