v3.3.0 (#525)

* feat: directory-scoped cheatpaths

`cheat` now searches for a `.cheat` directory in the current working
directory. If found, that directory is (temporarily) appended to the slice
of cheatpaths.

* makefile wip

* fix: appeases linter

Appeases linter (`go vet`) by adding quotation marks to YAML struct
tags.

* chore: modifies .gitignore

Adds `tag` to `.gitignore`

* feat: adds Makefile

Adds a `Makefile` for managing build-related tasks.

* chore: documents directory-local paths

Adds documentation regarding the new directory-local cheatpath
functionality.

* chore: updates dependencies

* chore: bumps version to 3.3.0

* chore: updates bin scripts

- Removes `build_release.sh`
- Places deprecation notice in `build_devel.sh`, as its purpose has been
  superceded by the `Makefile`.

cmd/cheat/main.go

@@ -13,7 +13,7 @@ import (
 	"github.com/cheat/cheat/internal/config"
 )
 
-const version = "3.2.2"
+const version = "3.3.0"
 
 func main() {
 

cmd/cheat/str_config.go

@@ -61,5 +61,15 @@ cheatpaths:
     path: ~/.dotfiles/cheat/personal
     tags: [ personal ]
     readonly: false
+
+  # While it requires no specific configuration here, it's also worth noting
+  # that 'cheat' will automatically append directories named '.cheat' within
+  # the current working directory to the 'cheatpath'. This can be very useful
+  # if you'd like to closely associate cheatsheets with, for example, a
+  # directory containing source code.
+  #
+  # Such "directory-scoped" cheatsheets will be treated as the most "local"
+  # cheatsheets, and will override less "local" cheatsheets. Likewise,
+  # directory-scoped cheatsheets will always be editable ('readonly: false').
 `)
 }