Commit da516b9f authored by Philipp C. H's avatar Philipp C. H Committed by Marcia Ramos

replace passive with active voice

parent 95c2791b
...@@ -8,7 +8,7 @@ projects by providing an advanced editor with commit staging. ...@@ -8,7 +8,7 @@ projects by providing an advanced editor with commit staging.
## Open the Web IDE ## Open the Web IDE
The Web IDE can be opened when viewing a file, from the repository file list, You can open the Web IDE when viewing a file, from the repository file list,
and from merge requests. and from merge requests.
![Open Web IDE](img/open_web_ide.png) ![Open Web IDE](img/open_web_ide.png)
...@@ -45,7 +45,7 @@ Single file editing is based on the [Ace Editor](https://ace.c9.io). ...@@ -45,7 +45,7 @@ Single file editing is based on the [Ace Editor](https://ace.c9.io).
## Stage and commit changes ## Stage and commit changes
After making your changes, click the Commit button in the bottom left to After making your changes, click the **Commit** button in the bottom left to
review the list of changed files. Click on each file to review the changes and review the list of changed files. Click on each file to review the changes and
click the tick icon to stage the file. click the tick icon to stage the file.
...@@ -67,10 +67,11 @@ shows you a preview of the merge request diff if you commit your changes. ...@@ -67,10 +67,11 @@ shows you a preview of the merge request diff if you commit your changes.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19279) in [GitLab Core][ce] 11.0. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19279) in [GitLab Core][ce] 11.0.
The Web IDE can be used to quickly fix failing tests by opening the branch or You can use the Web IDE to quickly fix failing tests by opening
merge request in the Web IDE and opening the logs of the failed job. The status the branch or merge request in the Web IDE and opening the logs of the failed
of all jobs for the most recent pipeline and job traces for the current commit job. You can access the status of all jobs for the most recent pipeline and job
can be accessed by clicking the **Pipelines** button in the top right. traces for the current commit by clicking the **Pipelines** button in the top
right.
The pipeline status is also shown at all times in the status bar in the bottom The pipeline status is also shown at all times in the status bar in the bottom
left. left.
...@@ -79,31 +80,31 @@ left. ...@@ -79,31 +80,31 @@ left.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19318) in [GitLab Core][ce] 11.0. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19318) in [GitLab Core][ce] 11.0.
Switching between your authored and assigned merge requests can be done without To switch between your authored and assigned merge requests, click the
leaving the Web IDE. Click the dropdown in the top of the sidebar to open a list dropdown in the top of the sidebar to open a list of merge requests. You will
of merge requests. You will need to commit or discard all your changes before need to commit or discard all your changes before switching to a different merge
switching to a different merge request. request.
## Switching branches ## Switching branches
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20850) in [GitLab Core][ce] 11.2. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20850) in [GitLab Core][ce] 11.2.
Switching between branches of the current project repository can be done without To switch between branches of the current project repository, click the dropdown
leaving the Web IDE. Click the dropdown in the top of the sidebar to open a list in the top of the sidebar to open a list of branches.
of branches. You will need to commit or discard all your changes before You will need to commit or discard all your changes before switching to a
switching to a different branch. different branch.
## Client Side Evaluation ## Client Side Evaluation
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19764) in [GitLab Core][ce] 11.2. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19764) in [GitLab Core][ce] 11.2.
The Web IDE can be used to preview JavaScript projects right in the browser. You can use the Web IDE to preview JavaScript projects right in the browser.
This feature uses CodeSandbox to compile and bundle the JavaScript used to This feature uses CodeSandbox to compile and bundle the JavaScript used to
preview the web application. preview the web application.
![Web IDE Client Side Evaluation](img/clientside_evaluation.png) ![Web IDE Client Side Evaluation](img/clientside_evaluation.png)
Additionally, for public projects an `Open in CodeSandbox` button is available Additionally, for public projects an **Open in CodeSandbox** button is available
to transfer the contents of the project into a public CodeSandbox project to to transfer the contents of the project into a public CodeSandbox project to
quickly share your project with others. quickly share your project with others.
...@@ -115,9 +116,9 @@ GitLab.com ...@@ -115,9 +116,9 @@ GitLab.com
![Admin Client Side Evaluation setting](img/admin_clientside_evaluation.png) ![Admin Client Side Evaluation setting](img/admin_clientside_evaluation.png)
Once it has been enabled in application settings, projects with a Once you have done that, you can preview projects with a `package.json` file and
`package.json` file and a `main` entry point can be previewed inside of the Web a `main` entry point inside the Web IDE. An example `package.json` is shown
IDE. An example `package.json` is below. below.
```json ```json
{ {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment