1. 31 Jan, 2020 1 commit
  2. 22 Oct, 2019 1 commit
    • Robert Marshall's avatar
      Make documentation linter show target path · 292c70cb
      Robert Marshall authored
      - We are seeing flaky documentation lint checks that do not always catch
        when a file inside the documentation is set with the executable bit.
        The check to find executable documents runs inside a subshell and its
        error output is not being redirected, nor would it count those errors
        when running `wc -l`. It seems implausible that we are failing to `cd`
        into the correct directory, but this is the one method I know of that
        would cause the `find` expression to fail silently in the logs. It is
        also just useful to see that yes, we are running the documentation
        linter against a reasonable directory in the logs.
      
      Related #28010Signed-off-by: Robert Marshall's avatarRobert Marshall <rmarshall@gitlab.com>
      292c70cb
  3. 11 Oct, 2019 1 commit
  4. 13 Sep, 2019 1 commit
  5. 16 Jul, 2019 1 commit
  6. 05 May, 2019 3 commits
  7. 01 May, 2019 2 commits
  8. 21 Feb, 2019 1 commit
  9. 20 Feb, 2019 1 commit
  10. 29 Aug, 2018 1 commit
  11. 26 Mar, 2018 1 commit
  12. 25 Sep, 2017 2 commits
  13. 01 May, 2017 1 commit
  14. 06 Dec, 2016 1 commit
  15. 16 Oct, 2016 1 commit
    • Robert Speicher's avatar
      Convert CHANGELOG to Markdown · 9f7a7115
      Robert Speicher authored
      All this does is convert the version sections into headers. The list
      items shouldn't really be indented by two spaces, but it makes no
      difference to the rendering and this way we retain authorship history
      for the actual changes.
      
      Related to gitlab-org/release-tools!29
      9f7a7115
  16. 19 Sep, 2016 1 commit
  17. 08 Aug, 2016 1 commit