1. 29 Mar, 2019 1 commit
  2. 27 Mar, 2019 1 commit
    • Gabriel Mazetto's avatar
      Upgrade `gitlab-markup` to 1.7.0 · e5af7d83
      Gabriel Mazetto authored
      The new version requires `python3` to be available. In omnibus
      installation this is already a reality as we are currently pathing
      previous `gitlab-markup` version to use `python3` instead of `python2`.
      
      We are now requiring `python3` with the gem without having to patch it.
      
      As a consequence to also make it easy to use it in development, we've
      introduced a `Pipfile` and `Pipfile.lock`, working similarly to
      `Gemfile` and `Gemfile.lock`, and added documentation on how to use
      them.
      e5af7d83
  3. 13 Mar, 2019 1 commit
  4. 05 Mar, 2019 1 commit
  5. 25 Feb, 2019 1 commit
  6. 22 Feb, 2019 1 commit
    • Evan Read's avatar
      Ensure all lists are surrounded by new lines · eb866309
      Evan Read authored
      Markdown renderers find it easier to determine
      where lists start and end when lists are surrounded
      by new lines.
      
      For consistency, also ensure entries in the list
      are aligned when they span multipls lines.
      eb866309
  7. 11 Feb, 2019 1 commit
    • Yorick Peterse's avatar
      Refactor the upgrading from source docs · 4d101979
      Yorick Peterse authored
      Instead of requiring one separate document for every version (which is
      created by release managers), we now use a single document for both
      Community Edition and Enterprise Edition. This allows developers to add
      guidelines right away, instead of release managers having to determine
      what to add.
      
      Version specific upgrading instructions are placed in a separate
      section. This prevents instructions from lingering around for many
      versions should a developer forget to remove them. This also ensures
      that all instructions are kept in a single place, instead of being
      spread across different documents.
      
      A minor downside is that CE and EE guidelines now live in the same
      document, which could cause merge conflicts. Since we are working
      towards a single codebase, this should only be an issue until we merge
      the codebases together; something we expect to do in the coming months.
      
      This commit also removes all old upgrading instructions, but these can
      still be accessed using Git branch specific URLs (included in the
      updating README).
      4d101979
  8. 06 Feb, 2019 3 commits
  9. 24 Jan, 2019 1 commit
  10. 18 Jan, 2019 1 commit
  11. 14 Jan, 2019 1 commit
  12. 08 Jan, 2019 1 commit
  13. 24 Dec, 2018 1 commit
  14. 17 Dec, 2018 1 commit
  15. 22 Nov, 2018 2 commits
  16. 06 Nov, 2018 1 commit
  17. 02 Nov, 2018 1 commit
  18. 01 Nov, 2018 1 commit
  19. 29 Oct, 2018 1 commit
  20. 22 Oct, 2018 1 commit
  21. 19 Oct, 2018 1 commit
  22. 17 Oct, 2018 3 commits
  23. 16 Oct, 2018 1 commit
  24. 15 Oct, 2018 1 commit
  25. 11 Oct, 2018 1 commit
    • Rémy Coutable's avatar
      Improve the contributing documentation · bfd61295
      Rémy Coutable authored
      
      
      This removes duplicated content from CONTRIBUTING.md and consolidate
      everything under doc/development/contributing/.
      
      This also fixes missing links.
      
      Lastly, this moves the style guides from the "Implement design & UI
      elements" page to a new "Style guides" page.
      Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
      bfd61295
  26. 09 Oct, 2018 2 commits
  27. 04 Oct, 2018 1 commit
  28. 27 Sep, 2018 2 commits
  29. 24 Sep, 2018 1 commit
  30. 21 Sep, 2018 1 commit
  31. 10 Sep, 2018 1 commit
  32. 06 Sep, 2018 1 commit
  33. 17 Aug, 2018 1 commit