diff options
| author | Yorick Peterse <yorickpeterse@gmail.com> | 2018-08-16 17:14:14 +0200 |
|---|---|---|
| committer | Yorick Peterse <yorickpeterse@gmail.com> | 2018-08-24 19:49:18 +0200 |
| commit | 1ee18c47c7e748339633c2ec3bf98169b56aaa2d (patch) | |
| tree | 8168a81001cd38e1d2ef9b56f12873ab94f37dbc /doc/development/README.md | |
| parent | 682c6ad931a67f7bbc76baad21af0d3b5d5b449d (diff) | |
| download | gitlab-ce-docs/abstraction-levels.tar.gz | |
Document abstraction levels and code reusedocs/abstraction-levels
This is based on the discussion in
https://gitlab.com/gitlab-org/gitlab-ce/issues/49653 and the example
merge request found at
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20908. The idea
is fairly straightforward: we define a variety of abstractions, then
state which can reuse which. This should ultimately foster _better_ code
reuse, make it easier to debug problems, and make it harder to
accidentally introduce a performance regression.
Diffstat (limited to 'doc/development/README.md')
| -rw-r--r-- | doc/development/README.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/development/README.md b/doc/development/README.md index fed3903c771..8449c1dd4f5 100644 --- a/doc/development/README.md +++ b/doc/development/README.md @@ -47,6 +47,7 @@ description: 'Learn how to contribute to GitLab.' - [How to dump production data to staging](db_dump.md) - [Working with the GitHub importer](github_importer.md) - [Working with Merge Request diffs](diffs.md) +- [Guidelines for reusing abstractions](reusing_abstractions.md) ## Performance guides |