Commit 17eb41a8 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis Committed by Sean Packham

Remove references to old settings location

parent 930eb111
# Project integrations # Project integrations
You can find the available integrations under the **Integrations** page by You can find the available integrations under your project's
navigating to the cog icon in the upper right corner of your project. You need **Settings ➔ Integrations** page. You need to have at least
to have at least [master permission][permissions] on the project. [master permission][permissions] on the project.
![Accessing the integrations](img/accessing_integrations.png)
## Project services ## Project services
......
...@@ -6,16 +6,11 @@ functionality to GitLab. ...@@ -6,16 +6,11 @@ functionality to GitLab.
## Accessing the project services ## Accessing the project services
You can find the available services under the **Integrations** page in your You can find the available services under your project's
project's settings. **Settings ➔ Integrations** page.
1. Navigate to the cog icon in the upper right corner of your project. You need There are more than 20 services to integrate with. Click on the one that you
to have at least [master permission][permissions] on the project. want to configure.
![Accessing the services](img/accessing_integrations.png)
1. There are more than 20 services to integrate with. Click on the one that you
want to configure.
![Project services list](img/project_services.png) ![Project services list](img/project_services.png)
......
...@@ -14,11 +14,8 @@ to the webhook URL. ...@@ -14,11 +14,8 @@ to the webhook URL.
Webhooks can be used to update an external issue tracker, trigger CI jobs, Webhooks can be used to update an external issue tracker, trigger CI jobs,
update a backup mirror, or even deploy to your production server. update a backup mirror, or even deploy to your production server.
Navigate to the webhooks page by going to the **Integrations** page from your Navigate to the webhooks page by going to your project's
project's settings which can be found under the wheel icon in the upper right **Settings ➔ Integrations**.
corner.
![Accessing the integrations](img/accessing_integrations.png)
## Webhook endpoint tips ## Webhook endpoint tips
......
# Pipelines settings # Pipelines settings
To reach the pipelines settings: To reach the pipelines settings navigate to your project's
**Settings ➔ CI/CD Pipelines**.
1. Navigate to your project and click the cog icon in the upper right corner.
![Project settings menu](../img/project_settings_list.png)
1. Select **Pipelines** from the menu.
The following settings can be configured per project. The following settings can be configured per project.
......
...@@ -30,11 +30,8 @@ See the [Changelog](#changelog) section for changes over time. ...@@ -30,11 +30,8 @@ See the [Changelog](#changelog) section for changes over time.
To protect a branch, you need to have at least Master permission level. Note To protect a branch, you need to have at least Master permission level. Note
that the `master` branch is protected by default. that the `master` branch is protected by default.
1. Navigate to the main page of the project. 1. Navigate to your project's **Settings ➔ Repository**
1. In the upper right corner, click the settings wheel and select **Protected branches**. 1. Scroll to find the **Protected branches** section.
![Project settings list](img/project_settings_list.png)
1. From the **Branch** dropdown menu, select the branch you want to protect and 1. From the **Branch** dropdown menu, select the branch you want to protect and
click **Protect**. In the screenshot below, we chose the `develop` branch. click **Protect**. In the screenshot below, we chose the `develop` branch.
......
...@@ -38,9 +38,9 @@ repository to pull from and click on the **Mirror repository** checkbox. ...@@ -38,9 +38,9 @@ repository to pull from and click on the **Mirror repository** checkbox.
![New project](repository_mirroring/repository_mirroring_new_project.png) ![New project](repository_mirroring/repository_mirroring_new_project.png)
For an existing project, you can set up mirror pulling by visiting the For an existing project, you can set up mirror pulling by visiting your project's
**Mirror repository** page under the wheel icon in the upper right corner. **Settings ➔ Repository** and searching for the "Pull from a remote repository"
Check the 'Mirror repository' box and hit **Save changes** at the bottom. section. Check the "Mirror repository" box and hit **Save changes** at the bottom.
You have a few options to choose from one being the user who will be the author You have a few options to choose from one being the user who will be the author
of all events in the activity feed that are the result of an update. This user of all events in the activity feed that are the result of an update. This user
needs to have at least [master access][perms] to the project. Another option is needs to have at least [master access][perms] to the project. Another option is
...@@ -62,9 +62,9 @@ this branch to prevent any changes from being lost. ...@@ -62,9 +62,9 @@ this branch to prevent any changes from being lost.
## Pushing to a remote repository ## Pushing to a remote repository
You can set up mirror pushing to an existing GitLab project by visiting the For an existing project, you can set up mirror pushing by visiting your project's
**Mirror repository** page under the wheel icon in the upper right. Simply **Settings ➔ Repository** and searching for the "Push to a remote repository"
click the "Remote mirror repository" checkbox and fill in the Git URL of the section. Check the "Remote mirror repository" box and fill in the Git URL of the
repository to push to. Hit **Save changes** for the changes to take effect. repository to push to. Hit **Save changes** for the changes to take effect.
![Push settings](repository_mirroring/repository_mirroring_push_settings.png) ![Push settings](repository_mirroring/repository_mirroring_push_settings.png)
......
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