Commit Graph

12 Commits

Author SHA1 Message Date
GitLab Bot d2f4295270 Add latest changes from gitlab-org/gitlab@master 2021-10-28 12:10:22 +00:00
GitLab Bot 63a014fe28 Add latest changes from gitlab-org/gitlab@master 2021-09-21 09:12:21 +00:00
GitLab Bot 3f0db3db2a Add latest changes from gitlab-org/gitlab@master 2021-07-19 18:08:23 +00:00
GitLab Bot b3e13e0dfd Add latest changes from gitlab-org/gitlab@master 2021-06-02 06:09:48 +00:00
GitLab Bot f8bb64721a Add latest changes from gitlab-org/gitlab@master 2020-11-26 06:09:20 +00:00
GitLab Bot 98d7cc758f Add latest changes from gitlab-org/gitlab@master 2020-10-30 18:08:56 +00:00
GitLab Bot 602ea42669 Add latest changes from gitlab-org/gitlab@master 2020-04-13 21:09:38 +00:00
Evan Read dee72df589 Followup edit of documentation 2019-07-24 15:47:06 +00:00
Lin Jen-Shin b32f7d4891 Add doc for ServiceResponse 2019-06-24 17:24:25 +00:00
Evan Read d98560c1f5 Make unordered lists conform to styleguide
- Also makes other minor Markdown fixes that were near the main fixes.
2019-01-08 12:21:09 +10:00
Robert Speicher cd2f74ca6a
Resolve typos in Reusing Abstractions doc 2018-09-13 10:07:36 -05:00
Yorick Peterse b15d28b4c7
Document abstraction levels and code reuse
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.
2018-09-13 17:01:20 +02:00