1. 22 Nov, 2018 1 commit
  2. 12 Jan, 2017 1 commit
    • Horacio Sanson's avatar
      Add support for PlantUML diagrams in Asciidoc. · f986b4c4
      Horacio Sanson authored
      This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a
      PlantUML diagram all we need is to include a plantuml block like:
      [plantuml, id="myDiagram", width="100px", height="100px"]
      bob -> alice : ping
      alice -> bob : pong
      The plantuml block is substituted by an HTML img element with *src* pointing to
      an external PlantUML server.
      This MR also add a PlantUML integration section to the Administrator -> Settings
      page to configure the PlantUML rendering service and to enable/disable it.
      Closes: #17603
  3. 08 Jan, 2017 1 commit
    • Yorick Peterse's avatar
      Remove the project_authorizations.id column · de321fbb
      Yorick Peterse authored
      This column used to be a 32 bits integer, allowing for only a maximum of
      2 147 483 647 rows. Given enough users one can hit this limit pretty
      quickly, as was the case for GitLab.com.
      Changing this type to bigint (= 64 bits) would give us more space, but
      we'd eventually hit the same limit given enough users and projects. A
      much more sustainable solution is to simply drop the "id" column.
      There were only 2 lines of code depending on this column being present,
      and neither truly required it to be present. Instead the code now uses
      the "project_id" column combined with the "user_id" column. This means
      that instead of something like this:
          DELETE FROM project_authorizations
          WHERE user_id = X
          AND id = Y;
      We now run the following when removing rows:
          DELETE FROM project_authorizations
          WHERE user_id = X
          AND project_id = Y;
      Since both user_id and project_id are indexed this should not slow down
      the DELETE query.
      This commit also removes the "dependent: destroy" clause from the
      "project_authorizations" relation in the User and Project models.
      Keeping this prevents Rails from being able to remove data as it relies
      on an "id" column being present. Since the "project_authorizations"
      table has proper foreign keys set up (with cascading removals) we don't
      need to depend on any Rails logic.
  4. 15 Sep, 2016 2 commits
  5. 31 Aug, 2016 1 commit
  6. 30 Aug, 2016 1 commit
  7. 04 Aug, 2016 1 commit
  8. 01 Aug, 2016 1 commit
  9. 16 Jun, 2016 2 commits
  10. 09 Jun, 2016 1 commit
    • Sean McGivern's avatar
      Enable RuboCop for migrations · 98bb435f
      Sean McGivern authored
      Migrations shouldn't fail RuboCop checks - especially lint checks, such
      as the nested method check. To avoid changing code in existing
      migrations, add the magic comment to the top of each of them to skip
      that file.
  11. 03 Jun, 2016 2 commits
  12. 25 May, 2016 1 commit
  13. 19 May, 2016 2 commits
  14. 12 May, 2016 2 commits