Commit 2cdfe183 authored by Amy Qualls's avatar Amy Qualls

Merge branch 'docs-source-code-old-ver-rem' into 'master'

Remove outdated GitLab versions from Source Code docs

See merge request gitlab-org/gitlab!71857
parents d1e8ac13 dcfa7dd5
...@@ -2,18 +2,15 @@ ...@@ -2,18 +2,15 @@
stage: Create stage: Create
group: Source Code group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments" info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
type: reference, howto
disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html' disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html'
--- ---
# GitLab Git Large File Storage (LFS) Administration **(FREE SELF)** # GitLab Git Large File Storage (LFS) Administration **(FREE SELF)**
> - Git LFS is supported in GitLab starting with version 8.2.
> - Support for object storage, such as AWS S3, was introduced in 10.0.
> - LFS is enabled in GitLab self-managed instances by default.
Documentation about how to use Git LFS are under [Managing large binary files with Git LFS doc](../../topics/git/lfs/index.md). Documentation about how to use Git LFS are under [Managing large binary files with Git LFS doc](../../topics/git/lfs/index.md).
LFS is enabled in GitLab self-managed instances by default.
## Requirements ## Requirements
- Users need to install [Git LFS client](https://git-lfs.github.com) version 1.0.1 or later. - Users need to install [Git LFS client](https://git-lfs.github.com) version 1.0.1 or later.
...@@ -346,8 +343,6 @@ git lfs version ...@@ -346,8 +343,6 @@ git lfs version
## Known limitations ## Known limitations
- Support for removing unreferenced LFS objects was added in 8.14 onward.
- LFS authentications via SSH was added with GitLab 8.12.
- Only compatible with the Git LFS client versions 1.1.0 and later, or 1.0.2. - Only compatible with the Git LFS client versions 1.1.0 and later, or 1.0.2.
- The storage statistics count each LFS object for - The storage statistics count each LFS object for
every project linking to it. every project linking to it.
...@@ -2,7 +2,6 @@ ...@@ -2,7 +2,6 @@
stage: Create stage: Create
group: Source Code group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments" info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
type: reference, api
--- ---
# Commits API **(FREE)** # Commits API **(FREE)**
...@@ -75,8 +74,6 @@ Example response: ...@@ -75,8 +74,6 @@ Example response:
## Create a commit with multiple files and actions ## Create a commit with multiple files and actions
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6096) in GitLab 8.13.
Create a commit by posting a JSON payload Create a commit by posting a JSON payload
```plaintext ```plaintext
...@@ -256,8 +253,6 @@ Example response: ...@@ -256,8 +253,6 @@ Example response:
## Get references a commit is pushed to ## Get references a commit is pushed to
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/15026) in GitLab 10.6
Get all references (from branches or tags) a commit is pushed to. Get all references (from branches or tags) a commit is pushed to.
The pagination parameters `page` and `per_page` can be used to restrict the list of references. The pagination parameters `page` and `per_page` can be used to restrict the list of references.
...@@ -291,8 +286,6 @@ Example response: ...@@ -291,8 +286,6 @@ Example response:
## Cherry-pick a commit ## Cherry-pick a commit
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8047) in GitLab 8.15.
Cherry-picks a commit to a given branch. Cherry-picks a commit to a given branch.
```plaintext ```plaintext
...@@ -366,8 +359,6 @@ dry run. ...@@ -366,8 +359,6 @@ dry run.
## Revert a commit ## Revert a commit
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22919) in GitLab 11.5.
Reverts a commit in a given branch. Reverts a commit in a given branch.
```plaintext ```plaintext
...@@ -622,7 +613,7 @@ Example response: ...@@ -622,7 +613,7 @@ Example response:
## Commit status ## Commit status
In GitLab 8.1 and later, this is the new commit status API. This is the commit status API for use with GitLab.
### List the statuses of a commit ### List the statuses of a commit
...@@ -752,8 +743,6 @@ Example response: ...@@ -752,8 +743,6 @@ Example response:
## List Merge Requests associated with a commit ## List Merge Requests associated with a commit
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/18004) in GitLab 10.7.
Get a list of Merge Requests related to the specified commit. Get a list of Merge Requests related to the specified commit.
```plaintext ```plaintext
......
...@@ -2,7 +2,6 @@ ...@@ -2,7 +2,6 @@
stage: Create stage: Create
group: Source Code group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments" info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
type: reference, api
--- ---
# Merge request approvals API **(PREMIUM)** # Merge request approvals API **(PREMIUM)**
...@@ -15,8 +14,7 @@ in the project. Must be authenticated for all endpoints. ...@@ -15,8 +14,7 @@ in the project. Must be authenticated for all endpoints.
### Get Configuration ### Get Configuration
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
You can request information about a project's approval configuration using the You can request information about a project's approval configuration using the
following endpoint: following endpoint:
...@@ -44,8 +42,7 @@ GET /projects/:id/approvals ...@@ -44,8 +42,7 @@ GET /projects/:id/approvals
### Change configuration ### Change configuration
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
If you are allowed to, you can change approval configuration using the following If you are allowed to, you can change approval configuration using the following
endpoint: endpoint:
...@@ -180,7 +177,7 @@ GET /projects/:id/approval_rules ...@@ -180,7 +177,7 @@ GET /projects/:id/approval_rules
### Get a single project-level rule ### Get a single project-level rule
> - Introduced 13.7. > Introduced in GitLab 13.7.
You can request information about a single project approval rules using the following endpoint: You can request information about a single project approval rules using the following endpoint:
...@@ -527,8 +524,7 @@ Configuration for approvals on a specific Merge Request. Must be authenticated f ...@@ -527,8 +524,7 @@ Configuration for approvals on a specific Merge Request. Must be authenticated f
### Get Configuration ### Get Configuration
> - Introduced in GitLab 8.9. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
You can request information about a merge request's approval status using the You can request information about a merge request's approval status using the
following endpoint: following endpoint:
...@@ -574,8 +570,7 @@ GET /projects/:id/merge_requests/:merge_request_iid/approvals ...@@ -574,8 +570,7 @@ GET /projects/:id/merge_requests/:merge_request_iid/approvals
### Change approval configuration ### Change approval configuration
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
If you are allowed to, you can change `approvals_required` using the following If you are allowed to, you can change `approvals_required` using the following
endpoint: endpoint:
...@@ -955,8 +950,7 @@ These are system generated rules. ...@@ -955,8 +950,7 @@ These are system generated rules.
## Approve Merge Request ## Approve Merge Request
> - Introduced in GitLab 8.9. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
If you are allowed to, you can approve a merge request using the following If you are allowed to, you can approve a merge request using the following
endpoint: endpoint:
...@@ -1019,8 +1013,7 @@ does not match, the response code is `409`. ...@@ -1019,8 +1013,7 @@ does not match, the response code is `409`.
## Unapprove Merge Request ## Unapprove Merge Request
> - Introduced in GitLab 9.0. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
If you did approve a merge request, you can unapprove it using the following If you did approve a merge request, you can unapprove it using the following
endpoint: endpoint:
......
...@@ -2,7 +2,6 @@ ...@@ -2,7 +2,6 @@
stage: Create stage: Create
group: Source Code group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments" info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
type: concepts, howto
--- ---
# Branches **(FREE)** # Branches **(FREE)**
...@@ -57,8 +56,6 @@ To compare branches in a repository: ...@@ -57,8 +56,6 @@ To compare branches in a repository:
## Delete merged branches ## Delete merged branches
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6449) in GitLab 8.14.
![Delete merged branches](img/delete_merged_branches.png) ![Delete merged branches](img/delete_merged_branches.png)
This feature allows merged branches to be deleted in bulk. Only branches that This feature allows merged branches to be deleted in bulk. Only branches that
...@@ -83,8 +80,6 @@ Search results appear in the following order: ...@@ -83,8 +80,6 @@ Search results appear in the following order:
## Branch filter search box ## Branch filter search box
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22166) in GitLab 11.5.
![Branch filter search box](img/branch_filter_search_box_v13_12.png) ![Branch filter search box](img/branch_filter_search_box_v13_12.png)
This feature allows you to search and select branches quickly. Search results appear in the following order: This feature allows you to search and select branches quickly. Search results appear in the following order:
......
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