GitLive Documentation

Extend Git with real-time collaborative superpowers

• The future of social coding

Connect. See when your fellow contributors are online and which repos, branches and files they are working on.
Automated. Connect your issue tracker to share what issue you are working on based on your current branch.

• Resolve conflicts before they happen

Live. See others' local changes in the gutter of your editor and get notified the moment you make a conflicting change.
Patch. View diffs of other contributors' local files and cherry‑pick individual lines, files or complete working copies.

• Code together in real-time

Codeshare. Make voice and video calls directly from your editor and codeshare to see each others cursors.
Agnostic. Edit together simultaneously, interoperable between VS Code and all JetBrains IDEs.

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.