Git and SVN


Codenvy natively supports Git and SVN, which is installed in all pre-defined stacks. Versioning functionality is available in the IDE and in the terminal. When using the Git and SVN menu, commands are injected into the workspace runtime and all output is streamed into the consoles panels. The following sections are in reference to Codenvy’s IDE Git and SVN Menu.

The following sections describe how to connect and authenticate users to a remote git/svn repository. Any operations that involves authentication on the remote repository will need to be done via the IDE interface unless authentication is setup seperately for the workspace machine(terminal/commands). Authentication information setup through the following documentation are stored on Codenvy server for each user and can be used on any of the user workspaces.

Git Using SSH Keys

Private repositories will require a secure SSH connection and most developers who plan to push to a repo will clone it via SSH, so an SSH key pair needs to be generated. SSH keys are saved in user preferences, so you need to generate the SSH key only once and it will be used in all workspaces.

When cloning be sure to use the SSH URL like git@<git url>:<account>/<project>.git when importing a project from a git repository using SSH key authorization. Note: HTTPS git URL can only be used to push changes if you enable oAuth authentication as described in Git Using oAuth.

Generate New SSH Keys

SSH keys can be generated at Profile > Preferences > SSH > VCS. Use the Generate Key button and manually save the resulting key to your Git hosting provider account. When prompted to provide the hostname for your repo, make sure it is a bare hostname (no www or http/https) as in the example below.


After the key has been generated, you can view and copy it, and save to your repository hosting account.


Use Existing SSH Keys

You can upload an existing public key instead of creating a new SSH key. When uploading a key add the hostname (using no www or http/https - as in the example below). Note that the public key > view button will not be available with this option as the public file should be generated already.


Adding SSH Public Key to Repository Account

Each repository provider has their own specific way to upload SSH public keys. This is required to use features such as push from the Git or Subversion menu in the workspace.

Git SSH Examples

The following example is specific to GitHub and GitLab but can be used with all git or SVN repository providers that use SSH authentication. Please refer to documentation provided by other providers for additional assistance.

GitHub Example

To add the associated public key to a repository/account using click your user icon(top right) then settings > ssh and gpg keys > new ssh key. Give a title to your liking and paste the public key copied from Che into form.



GitLab Example

To add the associated public key to a git repository/account using click your user icon(top right) then Profile Settings > SSH Keys. Give a title to your liking and paste the public key copied from Codenvy into form.


BitBucket Example

You can setup ssh to a dedicated BitBucket Server. Each user will still need to setup their own SSH key for authentication to the BitBucket Server which will be similar to GitHub/GitLab SSH examples.




Import Project from Repository Using SSH

Import project from the IDE Workspace > Import Project > GIT/SUBVERSION menu.


Importing a project can also be done from the dashboard menu.


Git Using oAuth

GitHub oAuth

Setup oAuth at GitHub

oAuth for Github allows users via the IDE git menu to import projects using SSH “git@”, push to repository, and use pull request panel. To enable automatic SSH key upload to GitHub for users, register an application in your GitHub account Setting > oAuth Applications > Developer Applications with the callback http://<HOST_IP>:<SERVER_PORT>/wsmaster/api/oauth/callback:



Setup environment variables.

Set the following to environment variables in the codenvy.env file then start/restart the Codenvy server.

= http://${CHE_HOST_IP}:${SERVER_PORT}/wsmaster/api/oauth/callback

Using OAuth in Workspace

Once the oauth is setup, SSH keys are generated and uploaded automatically to GitHub by a user in workspace IDE Profile > Preferences > SSH > VCS by clicking the ‘Octocat’ icon.


Import Existing Project

Import project from the IDE Workspace > Import Project > GITHUB menu. When importing a project from GitHub using oauth key authorization you can use the https url like<account>/<project>.git.


Importing a project can also be done from the dashboard menu.

BitBucket Server oAuth

You can setup oAuth to a dedicated BitBucket Server to give users access to the pull request panel in their workspace. Each user will still need to setup their own SSH key for authentication to the BitBucket Server which will be similar to GitHub/GitLab SSH examples.

1. Generate Keys

SSH to your BitBucket Server instance and generate RSA key-pairs

# generate the key pairs
$ openssl genrsa -out private.pem 1024
# copy the key and pem to a location where it can be accessed
$ openssl rsa -in private.pem -pubout >`
$ openssl pkcs8 -topk8 -inform pem -outform pem -nocrypt -in private.pem -out privatepkcs8.pem

2. Setup Codenvy in BitBucket Server

In the Bitbucket Server as an Admin:

  1. Go to Administration -> Application Links
  2. Enter your Codenvy URL in the ‘application url’ field and press the ‘Create new link’ button.
  3. When the ‘Configure Application URL’ window appears press the ‘Continue’ button.
  4. In the ‘Link applications’ window fill in the following fields and press the ‘Continue’ button:
    • Application Name : Codenvy
    • Service Provider Name : Codenvy
    • Consumer key : {added by you} (Save this string, you will need it later)
    • Shared secret : {added by you}
    • Request Token URL : {your Bitbucket Server URL}/plugins/servlet/oauth/request-token
    • Access token URL : {your Bitbucket Server URL}/plugins/servlet/oauth/access-token
    • Authorize URL : {your Bitbucket Server URL}/plugins/servlet/oauth/authorize

3. Add Codenvy oAuth Info

In the following screen press the pencil icon to edit and select the ‘Incoming Authentication’ menu. Fill in the following fields in the ‘OAuth’ tab: - Consumer Key : {the consumer key from the previous step} - Consumer Name : Codenvy - Public Key : {the key from file} (The key must not contain ‘—–BEGIN PUBLIC KEY—–’ and ‘—–END PUBLIC KEY—–’ rows) - Consumer Callback : {your Codenvy URL>}/api/oauth/1.0/callback

4. Configure Codenvy Properties

In the codenvy.env file add (or change if they already exist): - bitbucket_consumer_key : the consumer key you have entered before - bitbucket_private_key : the key from privatepkcs8.pem file - (The key must not contain ‘—-BEGIN PRIVATE KEY—–’ and ‘—–END PRIVATE KEY—–’ rows) (The key must be specified as a single raw) - bitbucket_endpoint : replace the default Bitbucket url by your Bitbucket Server url

5. Restart Codenvy

Restart your Codenvy server to enable the integration.

GitLab oAuth

Currently it’s not possible for Codenvy to use oAuth integration with GitLab. Although GitLab supports oAuth for clone operations, pushes are not supported. You can track this GitLab issue in their issue management system.

SVN Using Username/Password

Import project from the IDE Workspace > Import Project > SUBVERSION menu. When importing a project from you can use the https url like https://<hostname>/<repo-name>.


Built-In Pull Request Panel

Within the Codenvy IDE there is a pull request panel to simplify the creation of pull requests for GitHub, BitBucket or Microsoft VSTS (with git) repositories.

Set Git Committer Name and Email

Committer name and email are set in Profile > Preferences > Git > Committer. Once set each commit will include this information.


Git Workspace Clients

After importing repository, you can perform the most common Git operations using interactive menus or as terminal commands. Terminal git commands require it’s own authentication setup, which means that keys generated in the IDE will work only when Git is used in the IDE menus. Git installed in a terminal is a different git system. You may generate keys in ~/.ssh there as well.


To faster access to the most frequently used git functionality one can use keyboard shortcuts. * Commit: Alt + c * Push to remote: Alt + Shift + c * Pull from remote: Alt + p * Work with branches: Ctrl + b * Compare current changes with the latest repository version: Ctrl + Alt + d

Git in the Project Explorer and editors

Files in project explorer and editor tabs can be colored according to their Git Status:


  • Green: new files that are staged in index.
  • Blue: files that contain changes.
  • Yellow: files that are not staged in index.

Editor displays change markers according to edited regions of the file:


  • Yellow marker: modified line(s).
  • Green marker: new line(s).
  • White triangle: removed line(s).

Committing changes

To commit your changes use the git commit window. To show it click Git -> Commit... from main menu or just use Alt + c shortcut.


You can select files which will be added to index and committed.

All files in the selected package / folder in the project explorer will be checked by default. After selecting files, type the commit message in the text area. Optionally you could select Amend previous commit to replace previous commit (for more details see git docs).

Push the commit to a remote repository by checking Push committed changes to checkbox and selecting branch to push into.

Click Commit to proceed (the Commit button is active as long as at least 1 file is selected and a commit message is present or Amend previous commit is checked).

Behavior for files in the list view is the same as in compare window (see Reviewing changed files section). Double clicking a file will open diff window with it.

Pushing changes to remote repository

To push your commits to remote use the git push dialog. To open it use Git -> Remotes... -> Push from main menu or Alt + Shift + c shortcut.


Then choose remote repository to push into and select local and remote branch. Optionally by checking Force push is possible to push with force. After this, hit Push button to proceed.

Pulling changes from remote repository

To get changes from remote repository use the git pull dialog. To open it use Git -> Remotes... -> Pull from main menu or Alt + p shortcut.


Then choose remote repository to pull from and select remote and local branch. Optionally by checking Rebase instead of merge is possible to keep your local commits on top (for more information see git docs). After this, hit Pull button to proceed.

Managing branches

To manage your git branches use branches window. To open it use Git -> Branches... from main menu or Ctrl + b shortcut.


In the middle of the window is placed a list of all branches in current project. It is possible to display only local or only remote branches by Show branches drop-down above.

Buttons in the bottom describes allowed actions with branches. To checkout, delete or rename a branch one should select branch from the list first.

Reviewing changed files

Git compare window is used to show files which was changed. This widget could be invoked from different places for different states, but the most frequently used way is to use Git -> Compare -> <Select-to-what> from main menu or use Ctrl + Alt + d shortcut to compare current state of code to the latest local commit. Another way is to select an object in project tree and click Git -> Select-to-what from item’s context menu. Note, this widget shows changed files in the selected object in project explorer. To see all changes select project folder. Note, if only one file was changed, diff window will be shown instead of compare window.


By default, affected files is listed as a tree. With Expand all directories and Collapse all directories buttons above the tree a user can adjust tree state. By clicking View as list button is possible to switch representation of changed files to a list, where each file is shown with its full path. To return to the tree view just click Group by directories button.


To view diff for a file select it and click Compare button or just double click on a file name.

Reviewing code changes with the diff window

With the diff window it is possible to review changes between two states of code. To view the diff, use Git->Compare-><Select-to-what> from main menu. If more than one file has changed the list of changed files will be opened first. To select a file to compare double-click on it or select a file then click the Compare button. Another way to open diff is to select a file in project explorer and use Git -> Select-to-what from context menu or directly from editor’s context menu.


Your changes are displayed in the left editor and the file being compared to is on the right. The left editor can be used for editing and fixing your changes.

When you have multiple files to review you have the ability to navigate under all the files that are changed. The number of files that are reviewable is displayed in the title of the wizard. Use Next and Previous buttons to navigate to the next or previous file correspondingly.

For a keyboard navigation between the files you can use: Alt + . for Next and Alt + , for Previous.

The Refresh button updates difference links between editors.