Adds remaining design documents from 2021 and 2022
requested to merge ms/design-docs-migration/migrate-remaining-documents-21-22-without-cells into main
Why is this change being made?
Move Architecture Blueprints to Public Handbook (#279 - closed)
This MR adds all remaining design documents created in 2021 and 2022 from the gitlab project to the handbook project with proper metadata. See this section of the migration issue for info on how the migration was done.
Excerpt from design docs table. These documents are in this MR.
| Design document folder | Creation Date | Migrated? | Redirect? |
|---|---|---|---|
| graphql_api | 2021-01-07 | ||
| ci_scale | 2021-01-21 | ||
| consolidating_groups_and_projects | 2021-02-07 | ||
| ci_data_decay | 2021-09-10 | ||
| object_storage | 2021-11-18 | ||
| runner_scaling | 2022-01-19 | ||
| rate_limiting | 2022-09-08 | ||
| work_items | 2022-09-28 | ||
| runner_tokens | 2022-10-27 | ||
| observability_metrics | 2022-11-09 | ||
| remote_development | 2022-11-15 | ||
| secret_detection | 2022-11-25 | ||
| code_search_with_zoekt | 2022-12-28 |
|
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained bysection on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Adds remaining design documents from 2021 and 2022
Edited by Marc Saleiko