root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2024-07-18 21:30:18 +00:00
parent dad47fa737
commit 5402401b32
19 changed files with 131 additions and 74 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitlab-ci.yml
View File

@ -180,6 +180,8 @@ variables:
GET_SOURCES_ATTEMPTS: "3"
# CI_FETCH_REPO_GIT_STRATEGY: "none" is from artifacts. "clone" is from cloning
CI_FETCH_REPO_GIT_STRATEGY: "none"
FORCE_COLOR: 1
CLICOLOR_FORCE: 1
FLAKY_RSPEC_SUITE_REPORT_PATH: rspec/flaky/report-suite.json
FRONTEND_FIXTURES_MAPPING_PATH: crystalball/frontend_fixtures_mapping.json

2
.gitlab/ci/pages.gitlab-ci.yml
View File

@ -30,7 +30,7 @@ pages:
- mv $FLAKY_RSPEC_SUITE_REPORT_PATH public/$FLAKY_RSPEC_SUITE_REPORT_PATH || true
- mv $RSPEC_PACKED_TESTS_MAPPING_PATH.gz public/ || true
- mv $RSPEC_PACKED_TESTS_MAPPING_ALT_PATH.gz public/ || true
- mv $FRONTEND_FIXTURES_MAPPING_PATH public/ || true
- mv $FRONTEND_FIXTURES_MAPPING_PATH public/$FRONTEND_FIXTURES_MAPPING_PATH || true
- *compress-public
artifacts:
paths:

4
app/assets/javascripts/organizations/index/components/app.vue
View File

@ -79,8 +79,8 @@ export default {
<template>
<section>
<div v-if="showHeader" class="gl-display-flex gl-align-items-center">
<h1 class="gl-my-4 gl-font-size-h-display">{{ $options.i18n.organizations }}</h1>
<div v-if="showHeader" class="gl-flex gl-items-center">
<h1 class="gl-my-4 gl-text-size-h-display">{{ $options.i18n.organizations }}</h1>
<div class="gl-ml-auto">
<gl-button v-if="showNewOrganizationButton" :href="newOrganizationUrl" variant="confirm">{{
$options.i18n.newOrganization

8
app/assets/javascripts/organizations/shared/components/list/organizations_list_item.vue
View File

@ -10,7 +10,7 @@ export default {
showMore: __('Show more'),
showLess: __('Show less'),
},
truncateTextToggleButtonProps: { class: 'gl-font-sm!' },
truncateTextToggleButtonProps: { class: '!gl-text-sm' },
components: {
GlAvatarLabeled,
GlTruncateText,
@ -34,9 +34,7 @@ export default {
</script>
<template>
<li
class="organization-row gl-py-5 gl-px-5 gl-border-b gl-display-flex gl-align-items-flex-start"
>
<li class="organization-row gl-border-b gl-flex gl-items-start gl-px-5 gl-py-5">
<gl-avatar-labeled
:size="48"
:src="organization.avatarUrl"
@ -58,7 +56,7 @@ export default {
<div
v-safe-html:[$options.safeHtmlConfig]="organization.descriptionHtml"
data-testid="organization-description-html"
class="gl-text-secondary gl-font-sm md"
class="md gl-text-sm gl-text-secondary"
></div>
</gl-truncate-text>
</gl-avatar-labeled>

8
doc/development/fe_guide/frontend_goals.md
View File

@ -156,10 +156,10 @@ Ideally, we should reduce the number of times user needs to go through this long
The realistic goal is to move to _multiple SPAs_ experience where we define the _clusters_ of pages that form the user flow, and move this cluster from Rails routing to a single-page application with client-side routing. This way, we can load all the relevant context from HAML only once, and fetch all the additional data from the API depending on the route. An example of a cluster could be the following pages:
- issues list
- issue boards
- issue details page
- new issue
- **Issues** page
- **Issue boards** page
- **Issue details** page
- **New issue** page
- editing an issue
All of them have the same context (project path, current user etc.), we could easily fetch more data with issue-specific parameter (issue `iid`) and store the results on the client (so that opening the same issue won't require more API calls). This leads to a smooth user experience for navigating through issues.

4
doc/operations/incident_management/incidents.md
View File

@ -16,7 +16,7 @@ Use GitLab to triage, respond, and remediate incidents.
## Incidents list
When you [view the incidents list](manage_incidents.md#view-incidents-list), it contains the following:
When you [view the incidents list](manage_incidents.md#view-a-list-of-incidents), it contains the following:
- **State**: To filter incidents by their state, select **Open**, **Closed**,
or **All** above the incident list.
@ -177,7 +177,7 @@ label to the incident.
- [Create an incident](manage_incidents.md#create-an-incident)
- [Create an incident automatically](alerts.md#trigger-actions-from-alerts)
whenever an alert is triggered
- [View incidents list](manage_incidents.md#view-incidents-list)
- [View incidents list](manage_incidents.md#view-a-list-of-incidents)
- [Assign to a user](manage_incidents.md#assign-to-a-user)
- [Change incident severity](manage_incidents.md#change-severity)
- [Change incident status](manage_incidents.md#change-status)

14
doc/operations/incident_management/manage_incidents.md
View File

@ -34,25 +34,25 @@ To add an incident to an [iteration](../../user/group/iterations/index.md):
Alternatively, you can use the `/iteration` [quick action](../../user/project/quick_actions.md#issues-merge-requests-and-epics).
### From the incidents list
### From the Incidents page
Prerequisites:
- You must have at least the Reporter role for the project.
To create an incident from the incidents list:
To create an incident from the **Incidents** page:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Monitor > Incidents**.
1. Select **Create incident**.
### From the issues list
### From the Issues page
Prerequisites:
- You must have at least the Reporter role for the project.
To create an incident from the issues list:
To create an incident from the **Issues** page:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Plan > Issues**, and select **New issue**.
@ -117,9 +117,9 @@ To set up a webhook with PagerDuty:
To confirm the integration is successful, trigger a test incident from PagerDuty to
check if a GitLab incident is created from the incident.
## View incidents list
## View a list of incidents
To view the [incidents list](incidents.md#incidents-list):
To view a list of the [incidents](incidents.md#incidents-list):
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Monitor > Incidents**.
@ -151,7 +151,7 @@ To assign a user:
## Change severity
See [incident list](incidents.md#incidents-list) for a full description of the severity levels available.
See the [incidents list](incidents.md#incidents-list) topic for a full description of the severity levels available.
Prerequisites:

9
doc/user/application_security/policies/scan-execution-policies.md
View File

@ -429,3 +429,12 @@ this case, two SAST jobs run in the pipeline, one with the developer's variables
If you want to avoid running duplicate scans, you can either remove the scans from the project's `.gitlab-ci.yml` file or disable your
local jobs by setting `SAST_DISABLED: "true"`. Disabling jobs this way does not prevent the security jobs defined by scan execution
policies from running.
## Experimental features
DETAILS:
**Status:** Experiment has ended
This experiment has concluded and will not continue. After receiving feedback within this experiment, we will be focusing our efforts on a new policy type for enforcement of custom CI. The experiment will be removed in 17.3.
Learn more about the [pipeline execution policy](pipeline_execution_policies.md).

2
doc/user/application_security/vulnerabilities/index.md
View File

@ -92,9 +92,9 @@ The following data is shared with third-party AI APIs:
DETAILS:
**Tier:** Ultimate with [GitLab Duo Enterprise](../../../subscriptions/subscription-add-ons.md)
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
**Status:** Experiment
> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/10779) in GitLab 16.7 as an [experiment](../../../policy/experiment-beta-support.md#experiment) on GitLab.com.
> - [Generally available](https://gitlab.com/groups/gitlab-org/-/epics/10783) in GitLab 17.2.
Use GitLab Duo Vulnerability resolution to automatically create a merge request that
resolves the vulnerability. By default, it is powered by Anthropic's [`claude-3-haiku`](https://docs.anthropic.com/en/docs/about-claude/models#claude-3-a-new-generation-of-ai)

21
doc/user/gitlab_duo/index.md
View File

@ -118,16 +118,6 @@ DETAILS:
- LLM: Anthropic's [`claude-3-haiku`](https://docs.anthropic.com/en/docs/about-claude/models#claude-3-a-new-generation-of-ai).
- [View documentation](../application_security/vulnerabilities/index.md#explaining-a-vulnerability).
### Vulnerability resolution
DETAILS:
**Tier:** Ultimate with [GitLab Duo Enterprise](../../subscriptions/subscription-add-ons.md) add-on
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
- Help resolve a vulnerability by generating a merge request that addresses it.
- LLM: Anthropic's [`claude-3-haiku`](https://docs.anthropic.com/en/docs/about-claude/models#claude-3-a-new-generation-of-ai).
- [View documentation](../application_security/vulnerabilities/index.md#vulnerability-resolution).
## Beta features
### Merge request template population
@ -213,6 +203,17 @@ DETAILS:
- LLM: Vertex AI Codey [`text-bison`](https://console.cloud.google.com/vertex-ai/publishers/google/model-garden/text-bison)
- [View documentation](experiments.md#troubleshoot-failed-cicd-jobs-with-root-cause-analysis).
### Vulnerability resolution
DETAILS:
**Tier:** Ultimate with [GitLab Duo Enterprise](../../subscriptions/subscription-add-ons.md)
**Offering:** GitLab.com
**Status:** Experiment
- Help resolve a vulnerability by generating a merge request that addresses it.
- LLM: Anthropic's [`claude-3-haiku`](https://docs.anthropic.com/en/docs/about-claude/models#claude-3-a-new-generation-of-ai).
- [View documentation](../application_security/vulnerabilities/index.md#vulnerability-resolution).
### Product Analytics
DETAILS:

2
doc/user/gitlab_duo/use_cases.md
View File

@ -453,7 +453,7 @@ fun main() {
### Get Started with PowerShell
NOTE:
PowerShell support is [experimental](../project/repository/code_suggestions/supported_extensions.md#add-support-for-more-languages-for-code-suggestions-in-vs-code).
PowerShell support is [experimental](../project/repository/code_suggestions/supported_extensions.md#add-additional-languages-for-code-suggestions).
1. Use Duo Chat to ask how to get started with a PowerShell script that prints the file size of the current directory.

4
doc/user/project/import/jira.md
View File

@ -75,7 +75,7 @@ To import Jira issues to a GitLab project:
1. Select **Continue**. You're presented with a confirmation that import has started.
While the import is running in the background, you can navigate away from the import status page
to the issues page, and you can see the new issues appearing in the issues list.
While the import is running in the background, you can navigate
to the **Issues** page to see the new issues appearing in the list.
1. To check the status of your import, go to the Jira import page again.

2
doc/user/project/issues/confidential_issues.md
View File

@ -73,7 +73,7 @@ Confidential issues are hidden in search results for users without the necessary
## Confidential issue indicators
Confidential issues are visually different from regular issues in a few ways.
In the issues list and boards, you can see the confidential (**{eye-slash}**) icon
In the **Issues** and **Issue boards** pages, you can see the confidential (**{eye-slash}**) icon
next to issues marked as confidential.
If you don't have [enough permissions](#who-can-see-confidential-issues),

4
doc/user/project/issues/create_issues.md
View File

@ -120,7 +120,7 @@ example, if the list is scoped to a label `Frontend`, the new issue also has thi
## By sending an email
You can send an email to create an issue in a project on the project's
**Issues List** page.
**Issues** page.
Prerequisites:
@ -149,7 +149,7 @@ were you.
To regenerate the email address:
1. On the issues list, select **Email a new issue to this project**.
1. On the **Issues** page, select **Email a new issue to this project**.
1. Select **reset this token**.
## Using a URL with prefilled values

2
doc/user/project/issues/csv_import.md
View File

@ -40,7 +40,7 @@ You must have at least the Developer role for a project to import issues.
To import issues:
1. Go to your project's Issues list page.
1. Go to your project's **Issues** page.
1. Open the import feature, depending if the project has issues:
- The project has existing issues: in the upper-right corner, next to **Bulk edit**, select **Actions** (**{ellipsis_v}**) **> Import CSV**.
- The project has no issues: in the middle of the page, select **Import CSV**.

2
doc/user/project/issues/due_dates.md
View File

@ -37,7 +37,7 @@ The last way to set a due date is by using [quick actions](../quick_actions.md),
## Making use of due dates
You can see issues with their due dates in the issues list.
You can see issues with their due dates in the **Issues** page.
Overdue issues have their icon and date colored red.
To sort issues by their due dates, select **Due date** from the dropdown list on the right.
Issues are then sorted from the earliest due date to the latest.

6
doc/user/project/issues/managing_issues.md
View File

@ -143,7 +143,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed, GitLab Dedicated
#### From the issues list
#### From the Issues page
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15991) in GitLab 15.6.
@ -564,7 +564,7 @@ An issue can be assigned to one or [more users](multiple_assignees_for_issues.md
The assignees can be changed as often as needed. The idea is that the assignees are
people responsible for an issue.
When an issue is assigned to someone, it appears in their assigned issues list.
When an issue is assigned to someone, it appears in their **Assigned issues** page.
If a user is not a member of a project, an issue can only be assigned to them if they create it
themselves or another project member assigns them.
@ -623,7 +623,7 @@ To edit health status of an issue:
You can see the issue's health status in:
- Issues list
- The **Issues** page
- Epic tree
- Issue cards in issue boards

59
doc/user/project/repository/code_suggestions/supported_extensions.md
View File

@ -70,6 +70,57 @@ plugin support. Refer to the JetBrains documentation for specifics on your IDE.
For languages not listed in the table, Code Suggestions might not function as expected.
## Use open tabs as context
> - [Introduced](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/issues/206) in GitLab 17.2.
To enhance the accuracy and relevance of GitLab Duo Code Suggestions, enable the use of
open tabs as context in your IDE settings. This feature uses the contents of files most recently
opened or changed in your IDE to provide more tailored code suggestions, within certain truncation limits.
This extra context gives you:
- More accurate and relevant code suggestions
- Better alignment with your project's standards and practices
- Improved context for new file creation
Open tabs as context supports these languages:
- Code Completion: All configured languages.
- Code Generation: Go, Java, JavaScript, Kotlin, Python, Ruby, Rust, TypeScript (`.ts` and `.tsx` files),
Vue, and YAML.
## Enable open tabs as context
Prerequisites:
- Requires GitLab 17.1 or later.
- For GitLab self-managed instances, enable the `code_suggestions_context`and the
`advanced_context_resolver` [feature flags](../../../feature_flags.md).
- GitLab Duo Code Suggestions enabled for your project
- For Visual Studio Code, requires the GitLab Workflow extension, version 4.14.2 or later.
::Tabs
:::TabTitle Visual Studio Code
1. Install the [GitLab Workflow extension](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow)
from the Visual Studio Marketplace.
1. Configure the extension following the
[setup instructions](https://gitlab.com/gitlab-org/gitlab-vscode-extension#extension-settings).
1. Enable the feature by toggling the `gitlab.aiAssistedCodeSuggestions.enabledSupportedLanguages` setting.
:::TabTitle JetBrains IDEs
For installation instructions for JetBrains IDEs, see the
[GitLab JetBrains Plugin documentation](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin#toggle-sending-open-tabs-as-context).
::EndTabs
When you're ready to start coding:
1. Open relevant files, including configuration files, to provide better context.
1. Close any files you don't want to be used as context.
## View Multiple Code Suggestions
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/1325) in GitLab 17.1.
@ -85,13 +136,9 @@ might be available. To view all available suggestions:
- Select the right or left arrow to see next or previous options.
1. Press <kbd>Tab</kbd> to apply the suggestion you prefer.
## Experimental features
## Add additional languages for Code Suggestions
### Add support for more languages for Code Suggestions in VS Code
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/1318) as an [experiment](../../../../policy/experiment-beta-support.md) in GitLab 17.0.
If your desired language isn't a [supported language](#supported-languages) for Code Suggestions,
If your desired language isn't [enabled by default](#supported-languages) for Code Suggestions,
you can add support for it locally.
Prerequisites:

50
doc/user/shortcuts.md
View File

@ -30,17 +30,17 @@ These shortcuts are available in most areas of GitLab:
| Keyboard shortcut | Description |
|------------------------------------|-------------|
| <kbd>?</kbd> | Show or hide the shortcut reference sheet. |
| <kbd>Shift</kbd> + <kbd>p</kbd> | Go to your Projects page. |
| <kbd>Shift</kbd> + <kbd>g</kbd> | Go to your Groups page. |
| <kbd>Shift</kbd> + <kbd>a</kbd> | Go to your Activity page. |
| <kbd>Shift</kbd> + <kbd>l</kbd> | Go to your Milestones page. |
| <kbd>Shift</kbd> + <kbd>s</kbd> | Go to your Snippets page. |
| <kbd>Shift</kbd> + <kbd>p</kbd> | Go to your **Projects** page. |
| <kbd>Shift</kbd> + <kbd>g</kbd> | Go to your **Groups** page. |
| <kbd>Shift</kbd> + <kbd>a</kbd> | Go to your **Activity** page. |
| <kbd>Shift</kbd> + <kbd>l</kbd> | Go to your **Milestones** page. |
| <kbd>Shift</kbd> + <kbd>s</kbd> | Go to your **Snippets** page. |
| <kbd>s</kbd> / <kbd>/</kbd> | Put cursor in the search bar. |
| <kbd>f</kbd> | Put cursor in the filter bar. |
| <kbd>Shift</kbd> + <kbd>i</kbd> | Go to your Issues page. |
| <kbd>Shift</kbd> + <kbd>i</kbd> | Go to your **Issues** page. |
| <kbd>Shift</kbd> + <kbd>m</kbd> | Go to your [Merge requests](project/merge_requests/index.md) page. |
| <kbd>Shift</kbd> + <kbd>r</kbd> | Go to your Review requests page. |
| <kbd>Shift</kbd> + <kbd>t</kbd> | Go to your To-Do List page. |
| <kbd>Shift</kbd> + <kbd>r</kbd> | Go to your **Review requests** page. |
| <kbd>Shift</kbd> + <kbd>t</kbd> | Go to your **To-Do List** page. |
| <kbd>p</kbd>, then <kbd>b</kbd> | Show or hide the Performance Bar. |
| <kbd>Escape</kbd> | Hide tooltips or popovers. |
| <kbd>g</kbd>, then <kbd>x</kbd> | Toggle between [GitLab](https://gitlab.com/) and [GitLab Next](https://next.gitlab.com/) (GitLab SaaS only). |
@ -72,23 +72,23 @@ relatively quickly to work, and they take you to another page in the project.
| Keyboard shortcut | Description |
|-----------------------------|-------------|
| <kbd>g</kbd> + <kbd>o</kbd> | Go to the project overview page (**Project overview**). |
| <kbd>g</kbd> + <kbd>v</kbd> | Go to the project activity feed (**Manage > Activity**). |
| <kbd>g</kbd> + <kbd>r</kbd> | Go to the project releases list (**Deploy > Releases**). |
| <kbd>g</kbd> + <kbd>f</kbd> | Go to the [project files](#project-files) list (**Code > Repository**). |
| <kbd>g</kbd> + <kbd>o</kbd> | Go to the **Project overview** page. |
| <kbd>g</kbd> + <kbd>v</kbd> | Go to the project **Activity** page (**Manage > Activity**). |
| <kbd>g</kbd> + <kbd>r</kbd> | Go to the project **Releases** page (**Deploy > Releases**). |
| <kbd>g</kbd> + <kbd>f</kbd> | Go to the [project files](#project-files) (**Code > Repository**). |
| <kbd>t</kbd> | Open the project file search dialog. (**Code > Repository**, select **Find Files**). |
| <kbd>g</kbd> + <kbd>c</kbd> | Go to the project commits list (**Code > Commits**). |
| <kbd>g</kbd> + <kbd>n</kbd> | Go to the [repository graph](#repository-graph) page (**Code > Repository graph**). |
| <kbd>g</kbd> + <kbd>d</kbd> | Go to repository charts (**Analyze > Repository analytics**). |
| <kbd>g</kbd> + <kbd>i</kbd> | Go to the project issues list (**Plan > Issues**). |
| <kbd>i</kbd> | Go to the New Issue page (**Plan > Issues**, select **New issue** ). |
| <kbd>g</kbd> + <kbd>b</kbd> | Go to the project issue boards list (**Plan > Issue boards**). |
| <kbd>g</kbd> + <kbd>m</kbd> | Go to the project [merge requests](project/merge_requests/index.md) list (**Code > Merge requests**). |
| <kbd>g</kbd> + <kbd>p</kbd> | Go to the CI/CD pipelines list (**Build > Pipelines**). |
| <kbd>g</kbd> + <kbd>j</kbd> | Go to the CI/CD jobs list (**Build > Jobs**). |
| <kbd>g</kbd> + <kbd>e</kbd> | Go to the project environments (**Operate > Environments**). |
| <kbd>g</kbd> + <kbd>k</kbd> | Go to the project Kubernetes cluster integration page (**Operate > Kubernetes clusters**). You must have at least [`maintainer` permissions](permissions.md) to access this page. |
| <kbd>g</kbd> + <kbd>s</kbd> | Go to the project snippets list (**Code > Snippets**). |
| <kbd>g</kbd> + <kbd>c</kbd> | Go to the project **Commits** page (**Code > Commits**). |
| <kbd>g</kbd> + <kbd>n</kbd> | Go to the [Repository graph](#repository-graph) page (**Code > Repository graph**). |
| <kbd>g</kbd> + <kbd>d</kbd> | Go to the repository charts (**Analyze > Repository analytics**). |
| <kbd>g</kbd> + <kbd>i</kbd> | Go to the project **Issues** page (**Plan > Issues**). |
| <kbd>i</kbd> | Go to the **New Issue** page (**Plan > Issues**, select **New issue** ). |
| <kbd>g</kbd> + <kbd>b</kbd> | Go to the project **Issue boards** page (**Plan > Issue boards**). |
| <kbd>g</kbd> + <kbd>m</kbd> | Go to the project [Merge requests](project/merge_requests/index.md) page (**Code > Merge requests**). |
| <kbd>g</kbd> + <kbd>p</kbd> | Go to the CI/CD **Pipelines** page (**Build > Pipelines**). |
| <kbd>g</kbd> + <kbd>j</kbd> | Go to the CI/CD **Jobs** page (**Build > Jobs**). |
| <kbd>g</kbd> + <kbd>e</kbd> | Go to the project **Environments** page (**Operate > Environments**). |
| <kbd>g</kbd> + <kbd>k</kbd> | Go to the project **Kubernetes clusters** integration page (**Operate > Kubernetes clusters**). You must have at least [`maintainer` permissions](permissions.md) to access this page. |
| <kbd>g</kbd> + <kbd>s</kbd> | Go to the project **Snippets** page (**Code > Snippets**). |
| <kbd>g</kbd> + <kbd>w</kbd> | Go to the [project wiki](project/wiki/index.md) (**Plan > Wiki**), if enabled. |
| <kbd>.</kbd> | Open the [Web IDE](project/web_ide/index.md). |
@ -138,7 +138,7 @@ These shortcuts are available when browsing the files in a project (go to
| <kbd>↑</kbd> | Move selection up. |
| <kbd>↓</kbd> | Move selection down. |
| <kbd>Enter</kbd> | Open selection. |
| <kbd>Escape</kbd> | Go back to file list screen (only while searching for files, **Code > Repository**, then select **Find File**). |
| <kbd>Escape</kbd> | Go back to the **Find File** screen (only while searching for files, **Code > Repository**, then select **Find File**). |
| <kbd>y</kbd> | Go to file permalink (only while viewing a file). |
| <kbd>Shift</kbd> + <kbd>c</kbd> | Go to compare branches view. |
| <kbd>.</kbd> | Open the [Web IDE](project/web_ide/index.md). |