You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/development/backend/create_source_code_be/index.md
+21-12
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,14 @@ group: Source Code
4
4
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
5
5
---
6
6
7
-
# Create: Source Code backend
7
+
# Source Code Management
8
8
9
-
The Create: Source Code backend (BE) team focuses on the GitLab suite of Source Code Management
10
-
(SCM) tools. It is responsible for all backend aspects of the product categories
9
+
The Source Code Management team is responsible for all backend aspects of the product categories
11
10
that fall under the [Source Code group](https://about.gitlab.com/handbook/product/categories/#source-code-group)
12
11
of the [Create stage](https://about.gitlab.com/handbook/product/categories/#create-stage)
13
12
of the [DevOps lifecycle](https://about.gitlab.com/handbook/product/categories/#devops-stages).
14
13
15
-
We interface with the Gitaly and Code Review teams, and work closely with the
16
-
[Create: Source Code frontend team](https://about.gitlab.com/handbook/engineering/development/dev/create/create-source-code-fe/). The features
14
+
We interface with the Gitaly and Code Review teams. The features
17
15
we work with are listed on the
18
16
[Features by Group Page](https://about.gitlab.com/handbook/product/categories/features/#createsource-code-group).
19
17
@@ -35,17 +33,28 @@ For more information, refer to the [GitLab Shell documentation](../../gitlab_she
35
33
To learn about the reasoning behind our creation of `gitlab-sshd`, read the blog post
36
34
[Why we implemented our own SSHD solution](https://about.gitlab.com/blog/2022/08/17/why-we-have-implemented-our-own-sshd-solution-on-gitlab-sass/).
37
35
36
+
## CODEOWNERS
37
+
38
+
Source Code Management shares ownership of [Code Owners](../../code_owners/index.md) with the Code Review group.
39
+
38
40
## GitLab Rails
39
41
40
42
### Gitaly touch points
41
43
42
-
Gitaly is a Go RPC service which handles all the `git` calls made by GitLab.
43
-
GitLab is not exposed directly, and all traffic comes through Create: Source Code.
44
-
For more information, read [Gitaly touch points](gitaly_touch_points.md).
44
+
[Gitaly](../../../administration/gitaly/index.md) provides high-level RPC access to Git repositories.
45
+
It is present in every GitLab installation and coordinates Git repository storage and retrieval.
46
+
Gitaly implements a client-server architecture with Gitaly as the server and Gitaly clients, also
47
+
known as _Gitaly consumers_, including:
48
+
49
+
- GitLab Rails
50
+
- GitLab Shell
51
+
- GitLab Workhorse
45
52
46
-
### Source Code REST API Endpoints
53
+
Gitaly Rails provides API endpoints that are counterparts of Gitaly RPCs. For more information, read [Gitaly touch points](gitaly_touch_points.md).
47
54
48
-
Create: Source Code has over 100 REST endpoints, being a mixture of Grape API endpoints and Rails controller endpoints.
49
-
For a detailed list, refer to [Source Code REST Endpoints](rest_endpoints.md).
55
+
### Annotated Rails Source Code
50
56
51
-
An alternative list of the [Source Code endpoints and other owned objects](https://gitlab-com.gitlab.io/gl-infra/platform/stage-groups-index/source-code.html) is available.
57
+
The `:source_code_management` annotation indicates which code belongs to the Source Code Management
58
+
group in the Rails codebase. The annotated objects are presented on
59
+
[this page](https://gitlab-com.gitlab.io/gl-infra/platform/stage-groups-index/source-code.html) along
60
+
with the [Error Budgets dashboards](https://dashboards.gitlab.net/d/stage-groups-source_code/stage-groups3a-source-code3a-group-dashboard?orgId=1).
0 commit comments