`spec/fixtures/git-cheat-sheet.pdf` was checked in as an LFS file in
2019, but it's not really essential since it's just a test
fixture. Having this file causes some unintended headaches:

1. We now have to pay for LFS bandwidth for GitLab mirrors.

2. When a conflicting GitLab.com SSL cert is installed (e.g. due to
JAMF), a `git clone` will fail because of HTTPS verification. We've
seen a number of people blocked as a result.

While it's useful to dogfood LFS, the downsides seem to outweight the
upsides.

This Gem can be used to automatically resolve merge conflicts in
db/schema.rb. To use it you still need to initialise the configuration,
which can be done by running:

    merge_db_schema-init --force

See https://gitlab.com/gitlab-org/release/framework/issues/42 for more
information.

Signed-off-by: Rémy Coutable <remy@rymai.me>

See https://medium.com/@porteneuve/how-to-make-git-preserve-specific-files-while-merging-18c92343826b

[ci skip]

[ci skip]

[ci skip]

Signed-off-by: Rémy Coutable <remy@rymai.me>

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.

[ci skip]

Related to https://gitlab.com/gitlab-org/release-tools/merge_requests/29

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 https://gitlab.com/gitlab-org/release-tools/merge_requests/29