GitKraken Client Documentation

Downloads  
Contact support  
Feedback  
GitKraken.com  
GitKraken Status  

Workspaces

GitKraken Workspaces allow you to create easily accessible groups of repositories, take action across multiple repos, view details about their state at a glance, and share them with your team.


Access Workspaces

To access Workspaces, select the Workspace tab in the top left or use the Command Palette (command/ctrl + shift + P) and search “Open Workspaces”.


Cloud Workspaces

Cloud Workspaces will be available for you to work with on any machine and the selected teams within your organization. This helps ensure that everyone is up-to-date on the same set of repositories by offering multi-repository actions and the ability to work with all pull requests from these repositories.

Create a Cloud Workspace

To create a Cloud Workspace, select (or ). Then, select “Cloud Workspace”, name your Workspace, selecting the hosting service, and then select repositories to add. Optionally, you can also provide an icon, description and select teams or individual users to share with.

Note:
The integration for the desired service must be connected under Preferences > Integrations to create a Cloud Workspace.

Cloud multi-repository actions

Actions can be performed on multiple repositories within the Workspace at once, making it easy to get a new member of your team onboarded quickly or keep repository information up-to-date. To perform an action on multiple repositories, select the check box next to the repository name and then select the desired action from the options at the top.

The following multi-repository actions can be performed:

  • Clone: clone all selected repositories. HTTPS will be used by default unless you have SSH configured in your Integration settings.
  • Fetch: fetch all selected repositories.
  • Pull: pull all selected repositories. You can change the behavior of the pull button by selecting the dropdown and selecting the radio button next to the desired option.
  • Open in GitKraken Client or an external editor: open all selected repositories in GitKraken or in your default editor.
  • Locate in filesystem: point to all selected repositories locally or update the local location of the repositories if they have changed.
  • Remove: remove all selected repositories from the Workspace.

Pull requests

The Pull Request section will show all open pull requests for all repositories within the selected Workspace. Information shown here includes the pull request title, pull request number, CI status, complexity, the name of the branch being merged, and number of comments.

Complexity is a scale of 1 to 4 that scores a pull request’s complexity based on:

  • Number of lines changed
  • Number of files change
  • Number of commits made

To view a Workspaces pull requests, select a Workspace and then select Pull Requests.

Select Filter pull requests to filter for pull requests with the following options:

  • “Opened by Me”, to show pull requests that were opened by the user. This filter is available for GitHub, GitHub Enterprise Server, GitLab, and GitLab Self-Managed repositories.
  • “At Risk”, to show any pull requests that are not drafts and have been open for longer than 7 days. This filter is currently only available for GitHub, GitHub Enterprise Server, GitLab, and GitLab Self-Managed repositories.
  • “By repository”, to limit the view to a single repository within the Workspace. This filter is currently available for Azure DevOps, GitHub, GitHub Enterprise Server, Gitlab, and Gitlab Self-Managed repositories.

The search allows searching by pull request titles for all services. For GitHub.com Workspaces, GitHub’s search syntax can also be used.

At risk pull requests are pull requests that have not been updated in more than 7 days. This is indicated by the icon.

GitHub pull request view

If you are working with a GitHub.com Workspace, you may select a pull request to work with the GitHub pull request view.

Team view

On a Cloud Workspace, you will see a Team View section. This view shows all pull requests and issues for the repositories in your Workspace – giving you a high level view of your team’s coding efforts.

You can switch the Issue Tracker provider from the My Issues section in the Overview tab.

Team Pull Requests

This section of the Team View will show all Pull Requests related to your selected team.

The Team Pull Requests section has the following columns:

  • Last Updated
  • PR title with link to open the pull request in the hosting provider
  • PR Author
  • Repository name with link to open the reposotiry in GitKraken Client
  • Review status
  • PR status
    • Shows status for “Draft” or “At Risk” pull requests
  • Checks – Shows CI/CD results
  • Lines added/removed
  • PR branch
    • Double click to check out directly in GitKraken Client
  • GitHub.com Workspaces Only:
    • Shortcut to open the Pull Request Panel
    • Filter by assignee or author

Team Issues

Team Issues will show all GitHub Issues, GitLab Issues, Jira Cloud Issues, Jira Server, or Trello cards associated with the repo.

With Team Issues it is easy to switch between Jira or Trello and back to either GitHub Issues or GitLab Issues. If you select Jira or Trello, you can also filter by project so that you only see issues that matter to you.

View, edit and tie a branch to the issue with the Issue View from Workspace.


Local Workspaces

Local Workspaces allow you to create easily accessible groups of repositories, take actions across multiple repositories, view details about their state at a glance, and share them with your team.

Create a Local Workspace

To create a Local Workspace, select (or ). Then, select “Local Workspace”, name your Workspace, and browse to select repositories to add to your Local Workspace. You may select individual repositories, a directory of repositories, or a VS Code Workspace (.code-workspace). Optionally, you can also provide an icon and description.

Local multi-repository actions

Actions can be performed on multiple repositories within the Workspace at once. To perform an action on multiple repositories, select the check box next to the repository name and then select the desired action from the options at the top.

The following multi-repository actions can be performed:

  • Fetch: fetch all selected repositories.
  • Pull: pull all selected repositories. You can change the behavior of the pull button by selecting the dropdown and selecting the radio button next to the desired option.
  • Open in GitKraken Client or an external editor: open all selected repositories in GitKraken or in your default editor.
  • Remove: remove all selected repositories from the Workspace.

Create a Cloud Workspace from a Local Workspace

You can create a Cloud Workspace from a Local Workspace which will enable more visibility into your pull requests, issues, and share your Workspace with teams.

To do this, select your local Workspace to open it and then select Create cloud workspace. From here, you will need to select the provider for your new Cloud Workspace, select the repositories you would like added, and you can even add more repositories to this Workspace from the selected provider.

Note:
The integration for the desired service must be connected under Preferences > Integrations to create a Cloud Workspace.


Edit a Workspace

Edit a Workspace by selecting the ellipsis icon by the Workspace name.

You can adjust the content you want displayed for each view by selecting the settings .


View Repository Details

You may select the icon to open the repository details.


Repository statuses

Workspaces expose the state of all repositories so you can see the last checked-out branch, how many commits are ahead or behind the remote, and your work in progress with counts of modified added, deleted, and renamed files.


Workspace breadcrumb in toolbar

The option to remove the Workspace breadcrumb in the toolbar can be toggled under Preferences > UI Customization > Show Workspace breadcrumb in toolbar.

Requirement for Azure Workspaces and Insights

In order to work with Workspaces and Insights for Azure, Third-party application access via OAuth will need to be enabled in Azure from Organization Settings > Policies. You can find more information on this setting here.

Have feedback about this article? Did we miss something? Let us know!
On this page