An error occurred fetching the project authors.
- 06 Jul, 2021 1 commit
-
-
Ben Bodenmiller authored
-
- 17 Jun, 2021 1 commit
-
-
Alishan Ladhani authored
-
- 06 Apr, 2021 1 commit
-
-
Dylan Griffith authored
For 4 years we've had logic in our database migrations that required you to set a constant `DOWNTIME = true` if you required downtime and seek approval from the VP of Engineering. We have never once used this process as we've always found a way around the problem using a different approach. As such we decided in https://gitlab.com/gitlab-org/gitlab/-/issues/326495 that we should just remove this `DOWNTIME` constant and the extra checks here to reduce noise in our database code review and give less processes for people to learn. This MR removes a lot of things and here is a high level summary: 1. Remove DowntimeCheck class and the rake task that invoked and the CI job that invoked that rake task and any related tests, helper classes 2. Update documentation to make it clearer that downtime is not allowed and therefore remove the approval process 3. Update a page called `what_requires_downtime` to be called `avoiding_downtime_in_migrations` since it was already a set of patterns to avoid downtime and now it's worded more strongly to imply that we can always get away without downtime 4. Various other docs pages that had examples of migrations that used the `DOWNTIME` constant 5. Various rubocop specs that had migrations in them which used the `DOWNTIME` constant The one thing I did not do is go back and remove `DOWNTIME = false` from all the existing migrations. In general we should not be updating migrations once they've run and this would have made this MR change many thousands of files so it's not worth it.
-
- 29 Mar, 2021 1 commit
-
-
Jonathan Schafer authored
The work obviously is listed on the misused terms page https://about.gitlab.com/handbook/communication/top-misused-terms/
-
- 25 Mar, 2021 1 commit
-
-
Michelle Gill authored
-
- 11 Feb, 2021 1 commit
-
-
Alex Ives authored
-
- 29 Jan, 2021 1 commit
-
-
Amy Qualls authored
Continuing to clean up spelling issues from our docsets!
-
- 13 Jan, 2021 1 commit
-
-
Jerome Ng authored
Rename product analytics to intelligence docs
-
- 22 Dec, 2020 1 commit
-
-
Alina Mihaila authored
-
- 15 Dec, 2020 1 commit
-
-
Pavel Shutsin authored
-
- 11 Dec, 2020 1 commit
-
-
Jonston Chan authored
Replaces some shorthand words to enforce standard
-
- 08 Dec, 2020 1 commit
-
-
Craig Gomes authored
-
- 04 Dec, 2020 1 commit
-
-
Achilleas Pipinellis authored
The notation we use to represent a note is: ``` NOTE: **Note:** This is a note ``` This is rendered by Nanoc and presented in an alert box in the docs site. The second `**Note:**` can be redundant, so let's remove it.
-
- 23 Nov, 2020 1 commit
-
-
Achilleas Pipinellis authored
The previous URL had two drawbacks: 1. It didn't match what the title was about (`Assignments to DevOps Stages and Groups`, and the anchor was `#designated-technical-writers`). 2. It didn't account for the other sections, like development and API guidelines.
-
- 16 Nov, 2020 3 commits
-
-
Steve Abrams authored
Add a page for query performance guidelines with timing suggestions and a section on cold and warm cache. Link to the new doc from other database doc locations mentioning query times.
-
Marcel Amirault authored
-
Alper Akgun authored
-
- 10 Nov, 2020 1 commit
-
-
Marcel Amirault authored
We don't need NBSP spaces in the docs, and they can cause trouble when linting and using grep as they will not match on searches for spaces
-
- 02 Nov, 2020 1 commit
-
-
Jerome Ng authored
Update links to handbook
-
- 08 Oct, 2020 1 commit
-
-
jeromezng authored
This MR moves the docs from telemetry to product_analytics
-
- 03 Oct, 2020 1 commit
-
-
Craig Norris authored
-
- 28 Sep, 2020 1 commit
-
-
Andreas Brandl authored
-
- 23 Jul, 2020 1 commit
-
-
pbair authored
Update development docs for database reviews to cover changes to tracking of schema migration versions.
-
- 16 Jul, 2020 2 commits
-
-
Alina Mihaila authored
-
Marcel Amirault authored
Alert boxes should have a newline after the initial alert text itself. Find and replace to fix these.
-
- 11 Jun, 2020 1 commit
-
-
Doug Stull authored
- code moved
-
- 10 Jun, 2020 2 commits
-
-
Steve Abrams authored
to be more clear about risks when creating index in post-deployment migration.
-
Amy Qualls authored
More words that shouldn't be tracked by the spell checker.
-
- 29 Apr, 2020 1 commit
-
-
Toon Claes authored
The piece on schema changes was quite outdated, so I've replaced it with the new guidelines and the use of `bin/regenerate-schema`.
-
- 06 Apr, 2020 3 commits
-
-
Alper Akgun authored
-
Alper Akgun authored
-
Alper Akgun authored
-
- 02 Apr, 2020 2 commits
-
-
Mayra Cabrera authored
We've recently added new migrations cops, this MRs emphasizes no Cops should be disabled on db files
-
Adam Hegyi authored
-
- 24 Mar, 2020 1 commit
-
-
Mayra Cabrera authored
Reverts a1c6a1d3. We have 5 DB maintainers now on different timezones, even though the ratio of backend engineers per database maintainer is still not great (163:5), the chances of not having a maintainer available are fewer.
-
- 22 Mar, 2020 1 commit
-
-
Andreas Brandl authored
Relates to https://gitlab.com/gitlab-org/gitlab/issues/29465
-
- 16 Mar, 2020 1 commit
-
-
Toon Claes authored
When a new composite index is added, it might make an existing index redundant. So when adding an index, these redundant indexes should be removed in the same migration.
-
- 13 Mar, 2020 1 commit
-
-
Evan Read authored
Also fix violations of the rule.
-
- 12 Mar, 2020 1 commit
-
-
Evan Read authored
-
- 06 Mar, 2020 1 commit
-
-
João Cunha authored
-