1. 03 Jul, 2020 1 commit
  2. 01 May, 2020 1 commit
  3. 31 Oct, 2019 1 commit
  4. 16 Sep, 2019 1 commit
    • James Ennis's avatar
      CONTRIBUTING.rst: Add UI section · 163a4758
      James Ennis authored
      Now that the frontend has been mostly reworked/standardized,
      this patch attempts to put our some guidelines/information in
      around UI contributions.
      163a4758
  5. 13 Sep, 2019 1 commit
  6. 31 Jul, 2019 1 commit
  7. 29 May, 2019 1 commit
    • Benjamin Schubert's avatar
      Introduce Cython to the project and document · 4e9b5803
      Benjamin Schubert authored
      Cython requires a plugin to allow coverage of cython files, which
      was updated in coveragerc. It also means we need to build the
      dependencies and install cython for coverage.
      
      Cython requires access to both source and compiled files when
      running coverage. We therefore need to install project in develop
      mode.
      
      Updated documentation to explain how to run tests without tox but
      with coverage
      4e9b5803
  8. 21 May, 2019 1 commit
  9. 14 May, 2019 1 commit
  10. 29 Mar, 2019 1 commit
  11. 22 Feb, 2019 1 commit
  12. 20 Feb, 2019 1 commit
  13. 18 Feb, 2019 1 commit
  14. 11 Feb, 2019 1 commit
  15. 25 Jan, 2019 1 commit
  16. 21 Jan, 2019 1 commit
  17. 11 Jan, 2019 1 commit
  18. 10 Jan, 2019 1 commit
  19. 09 Jan, 2019 1 commit
  20. 04 Jan, 2019 1 commit
  21. 03 Jan, 2019 5 commits
  22. 13 Dec, 2018 1 commit
  23. 15 Nov, 2018 1 commit
  24. 08 Nov, 2018 3 commits
    • Angelos Evripiotis's avatar
      contributing: emphasise the 'why' in commits · f7643440
      Angelos Evripiotis authored
      Explain why it's useful to mention the decisions made for a change and
      provide links for background, e.g. issue numbers.
      
      My general experience of git histories is that folks don't do enough
      explaining, so it's great we have a contributing section for it.
      
      I've found it's easier for folks to stick to rules when they know the
      practical reasons for them, so provide some.
      f7643440
    • Angelos Evripiotis's avatar
      contributing: non-WIP should always be landable · f7231e90
      Angelos Evripiotis authored
      I was recently surprised that we don't prefer addressing review comments
      in 'fixup!' commits.
      
      Coming from GitHub, I've found that fixup commits make it easier for
      reviewers to see what has changed since their last review. The idea is
      to use '--autosquash' before landing to clean up the history again.
      
      It's a pleasant surprise that it's easy to keep track of what changed in
      merge-requests between pushes, so we can always keep the history clean.
      
      Document this, so folks like me can see the light sooner.
      f7231e90
    • Angelos Evripiotis's avatar
      contributing: WIP again to be kind to reviewers · c0a8bb66
      Angelos Evripiotis authored
      As someone coming from GitHub to GitLab, I was pleasantly surprised by
      the 'filter by WIP status' option.
      
      To make sure we get the most out of it, add a guideline to keep the
      filter clean, to reduce reviewer burden.
      c0a8bb66
  25. 16 Oct, 2018 1 commit
  26. 14 Oct, 2018 1 commit
  27. 09 Oct, 2018 7 commits
  28. 08 Oct, 2018 1 commit