An error occurred fetching the project authors.
  1. 06 Jul, 2021 1 commit
  2. 17 Jun, 2021 1 commit
  3. 06 Apr, 2021 1 commit
    • Dylan Griffith's avatar
      Remove migration downtime check since we do not allow downtime · 016c3969
      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.
      016c3969
  4. 29 Mar, 2021 1 commit
  5. 25 Mar, 2021 1 commit
  6. 11 Feb, 2021 1 commit
  7. 29 Jan, 2021 1 commit
  8. 13 Jan, 2021 1 commit
  9. 22 Dec, 2020 1 commit
  10. 15 Dec, 2020 1 commit
  11. 11 Dec, 2020 1 commit
  12. 08 Dec, 2020 1 commit
  13. 04 Dec, 2020 1 commit
    • Achilleas Pipinellis's avatar
      Remove redundant `**Note:**` from docs · f42f17ad
      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.
      f42f17ad
  14. 23 Nov, 2020 1 commit
    • Achilleas Pipinellis's avatar
      Update handbook URL for Technical Writers assignments · 2dc1b3be
      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.
      2dc1b3be
  15. 16 Nov, 2020 3 commits
  16. 10 Nov, 2020 1 commit
    • Marcel Amirault's avatar
      Remove NBSP spaces from docs · 3ac657f6
      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
      3ac657f6
  17. 02 Nov, 2020 1 commit
  18. 08 Oct, 2020 1 commit
  19. 03 Oct, 2020 1 commit
  20. 28 Sep, 2020 1 commit
  21. 23 Jul, 2020 1 commit
  22. 16 Jul, 2020 2 commits
  23. 11 Jun, 2020 1 commit
  24. 10 Jun, 2020 2 commits
  25. 29 Apr, 2020 1 commit
  26. 06 Apr, 2020 3 commits
  27. 02 Apr, 2020 2 commits
  28. 24 Mar, 2020 1 commit
  29. 22 Mar, 2020 1 commit
  30. 16 Mar, 2020 1 commit
  31. 13 Mar, 2020 1 commit
  32. 12 Mar, 2020 1 commit
  33. 06 Mar, 2020 1 commit