Skip to content
Snippets Groups Projects
Commit d060aaeb authored by Brendan Lynch's avatar Brendan Lynch
Browse files

Update links to new protected branches location

parent d0bc3d9f
No related branches found
No related tags found
1 merge request!136178Update links to new protected branches location
Pipeline #1450224163 skipped
Showing
with 16 additions and 16 deletions
......@@ -1418,7 +1418,7 @@ features:
- title : "Protected branches"
description: "Granular permissions for branches you want to protect."
link_description: "Read about protected branches"
link: https://docs.gitlab.com/ee/user/project/protected_branches.html
link: https://docs.gitlab.com/ee/user/project/repository/branches/protected.html
screenshot_url: 35-protected-branches.png
category:
- source_code_management
......@@ -1751,7 +1751,7 @@ features:
- title : "Restrict push and merge access"
description: "Extend the base functionality of protected branches and choose which users can push or merge to a protected branch."
link_description: "Read about protected branches"
link: https://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users
link: https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#restricting-push-and-merge-access-to-certain-users
screenshot_url: 39-restrict-push-and-merge-access-to-users.png
category:
- source_code_management
......@@ -4035,7 +4035,7 @@ features:
- title : "Per-environment permissions"
description: "Developers and QA can deploy to their own environments on demand while production stays locked down. Build engineers and ops teams spend less time servicing deploy requests, and can gate what goes into production."
link_description: "Learn about protected branches in GitLab"
link: "https://docs.gitlab.com/ee/user/project/protected_branches.html"
link: "https://docs.gitlab.com/ee/user/project/repository/branches/protected.html"
category:
- environment_management
gitlab_core: true
......
......@@ -3,7 +3,7 @@ features:
secondary:
- name: "Force push option for protected branches"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/protected_branches.html#allow-force-push-on-protected-branches'
documentation_link: 'https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#allow-force-push-on-protected-branches'
image_url: '/images/13_11/code_owners_approval_new_protected_branch_v13_10.png'
reporter: danielgruesso
stage: create
......
......@@ -3,7 +3,7 @@ features:
- name: "Allow Deploy Keys to push to protected branches"
available_in: [core, premium, ultimate]
gitlab_com: true
documentation_link: 'https://docs.gitlab.com/ee/user/project/protected_branches.html#allow-deploy-keys-to-push-to-a-protected-branch'
documentation_link: 'https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#allow-deploy-keys-to-push-to-a-protected-branch'
image_url: "/images/13_9/deploy_keys.png"
reporter: ogolowinski
stage: deploy
......
......@@ -10,7 +10,7 @@ features:
- 'Code Review'
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/344632'
description: |
To ensure that merge request approvals are about the latest proposed changes, you may [remove approvals when more changes are added](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/settings.html#remove-all-approvals-when-commits-are-added-to-the-source-branch). However, this kind of removal can be impractical if you also [require Code Owners to approve changes](https://docs.gitlab.com/ee/user/project/protected_branches.html#require-code-owner-approval-on-a-protected-branch) for specific files or paths. Even if the new changes don't affect the files that a Code Owner is responsible for, their approval is removed.
To ensure that merge request approvals are about the latest proposed changes, you may [remove approvals when more changes are added](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/settings.html#remove-all-approvals-when-commits-are-added-to-the-source-branch). However, this kind of removal can be impractical if you also [require Code Owners to approve changes](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#require-code-owner-approval-on-a-protected-branch) for specific files or paths. Even if the new changes don't affect the files that a Code Owner is responsible for, their approval is removed.
 
Now you can be more selective and only remove Code Owner approvals if their files changed, increasing the speed of code review by avoiding unnecessary re-approvals.
 
......
......@@ -11,7 +11,7 @@ features:
- Importers
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/384939'
description: |
When importing projects from GitHub to GitLab, the GitLab [**Allowed to push** branch protection rule](https://docs.gitlab.com/ee/user/project/protected_branches.html#configure-a-protected-branch) is set if the following conditions are met in the GitHub project:
When importing projects from GitHub to GitLab, the GitLab [**Allowed to push** branch protection rule](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#configure-a-protected-branch) is set if the following conditions are met in the GitHub project:
 
- The **Require a pull request before merging** setting is set.
- The **Allow specified actors to bypass required pull requests** setting lists some users.
......
......@@ -112,7 +112,7 @@ features:
information or private configuration options.
In order to avoid any data leakage, you can set the protected flag for a
specific GitLab Runner, so only jobs running on
[protected branches](https://docs.gitlab.com/ee/user/project/protected_branches.html)
[protected branches](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html)
are picked up.
 
Combining this feature with [mandatory approval](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/rules.html)
......
......@@ -260,7 +260,7 @@ features:
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/27742'
description: |
[Protected
branches](https://docs.gitlab.com/ee/user/project/protected_branches.html)
branches](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html)
allow you to lock down push or merge access to your repository's
branches, preventing inadvertent changes entering your code or enforcing
particular workflows.
......
......@@ -495,7 +495,7 @@ features:
 
- name: "Allow protected branches to be created by developers"
available_in: [core, starter, premium, ultimate]
documentation_link: "https://docs.gitlab.com/ee/user/project/protected_branches.html#creating-a-protected-branch"
documentation_link: "https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#creating-a-protected-branch"
reporter: jramsay
stage: create
issue_url: "https://gitlab.com/gitlab-org/gitlab-ce/issues/53361"
......
......@@ -52,7 +52,7 @@ features:
 
- name: "Code Owner Approvals for Protected Branches"
available_in: [premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/protected_branches.html#protected-branches-approval-by-code-owners-premium'
documentation_link: 'https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#protected-branches-approval-by-code-owners-premium'
image_url: '/images/12_4/protected-branches.png'
reporter: jramsay
stage: create
......
......@@ -47,7 +47,7 @@ to automatically protect all our stable releases by protecting `*-stable`.
 
![Wildcard Branch Protection in GitLab 8.10](/images/8_10/wc2.png)
 
[protected-branches]: https://docs.gitlab.com/ee/user/project/protected_branches.html
[protected-branches]: https://docs.gitlab.com/ee/user/project/repository/branhces/protected.html
 
## Merge into Protected Branches
 
......@@ -70,7 +70,7 @@ not from the command line).
Combine this feature with approvals (EE only) to enforce code review by multiple
people, while still giving developers the power to merge at their discretion.
 
> [See our documentation on protected branches](https://docs.gitlab.com/ee/user/project/protected_branches.html)
> [See our documentation on protected branches](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html)
 
## Improved Diffs
 
......
......@@ -93,7 +93,7 @@ to merge through a merge request to the branch.
For each action (push and merge) you can allow any amount of users and
permissions, making this a very powerful addition to GitLab EE for organizations.
 
> [Branch permissions for users Documentation](https://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users)
> [Branch permissions for users Documentation](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#restricting-push-and-merge-access-to-certain-users)
 
## Resolve Discussions in MRs
 
......
......@@ -176,7 +176,7 @@ Learn more about [Burndown Charts](https://docs.gitlab.com/ee/user/project/miles
 
Tags can quickly get out of hand and, depending on your workflow, you might want to control who can create or update tags. Protected Tags in GitLab 9.1 does just that, making it easy to prevent tags from being created or updated.
 
Using a very similar approach to [protected branches](https://docs.gitlab.com/ee/user/project/protected_branches.html), you can now control this easily for any of your projects. Much like protected branches, you can define who is able to create tags and use wildcard matching on your rules too.
Using a very similar approach to [protected branches](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html), you can now control this easily for any of your projects. Much like protected branches, you can define who is able to create tags and use wildcard matching on your rules too.
 
<i class="fas fa-book" aria-hidden="true"></i>
Learn more about [protected tags](https://docs.gitlab.com/ee/user/project/protected_tags.html#protected-tags) in our docs.
......
......@@ -75,7 +75,7 @@ Looking for a consolidated list of hardening recommendations? Use the links belo
### Protect your pipelines for all branches
**Admin > Settings > CI**
 
* Pipelines are a part of jobs that execute steps in stages to automate tasks on behalf of the users of a project. They are a central component of CI/CD. By default, only the default branch gets a protected pipeline. Configure your other branches with the same level of security by following [these simple steps](https://docs.gitlab.com/ee/user/project/protected_branches.html#configure-a-protected-branch). This considerably hardens your pipelines.
* Pipelines are a part of jobs that execute steps in stages to automate tasks on behalf of the users of a project. They are a central component of CI/CD. By default, only the default branch gets a protected pipeline. Configure your other branches with the same level of security by following [these simple steps](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#configure-a-protected-branch). This considerably hardens your pipelines.
* The security features enabled by default on protected pipelines are listed in our [documentation](https://docs.gitlab.com/ee/ci/pipelines/#pipeline-security-on-protected-branches).
* Once the pipeline has run, the code will be deployed in an environment. To limit interactions with that environment and to protect it from unauthorized users, you can set your key environments as protected.
* Prerequisites and full process are available in the [documentation](https://docs.gitlab.com/ee/ci/environments/protected_environments.html).
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment