Lint and clean markdown README

.github/workflows/ci.yml

@@ -7,7 +7,7 @@ on:
     - cron: '0 0 * * 0'
 
 jobs:
-  lint:
+  lint-code:
     runs-on: ubuntu-latest
 
     steps:
@@ -24,6 +24,17 @@ jobs:
       - name: Lint with tox
         run: tox -e check
 
+  lint-readme:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Clone repo
+        uses: actions/checkout@v2
+      - name: Lint README.md
+        uses: docker://avtodev/markdown-lint:v1
+        with:
+          args: './README.md'
+
   test:
     runs-on: ubuntu-latest
 

.markdownlintrc

@@ -0,0 +1,5 @@
+{
+    "default": true,
+    "line_length": false,
+    "MD041": false
+}

README.md

@@ -2,7 +2,7 @@
 
 # pass-git-helper
 
-[![Debian CI](https://badges.debian.net/badges/debian/testing/pass-git-helper/version.svg)](https://buildd.debian.org/pass-git-helper) 
+[![Debian CI](https://badges.debian.net/badges/debian/testing/pass-git-helper/version.svg)](https://buildd.debian.org/pass-git-helper)
 [![AUR](https://img.shields.io/aur/version/pass-git-helper.svg)](https://aur.archlinux.org/packages/pass-git-helper/)
 [![Homebrew](https://img.shields.io/badge/dynamic/json.svg?url=https://formulae.brew.sh/api/formula/pass-git-helper.json&query=$.versions.stable&label=homebrew)
 
@@ -15,10 +15,12 @@ It is recommended to configure GPG to use a graphical pinentry program.
 That way, you can also use this helper when [git] is invoked via GUI programs such as your IDE.
 For a configuration example, refer to the [ArchWiki](https://wiki.archlinux.org/index.php/GnuPG#pinentry).
 In case you really want to use the terminal for pinentry (via `pinentry-curses`), be sure to [appropriately configure the environment variable `GPG_TTY`](https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html), most likely by adding the following lines to your shell initialization:
+
 ```sh
 GPG_TTY=$(tty)
 export GPG_TTY
 ```
+
 If you use this setup for remote work via SSH, also consider the alternative of [GPG agent forwarding](https://wiki.gnupg.org/AgentForwarding).
 
 ## Installation
@@ -35,11 +37,13 @@ sudo pip install .
 
 This might potentially install Python packages without the knowledge of your system's package manager.
 If all package preconditions are already met, you can also copy the script file to to your system to avoid this problem:
+
 ```sh
 sudo cp passgithelper.py /usr/local/bin/pass-git-helper
 ```
 
 Another option is to install the script in an isolated [virtualenv](https://virtualenv.pypa.io/en/latest/):
+
 ```sh
 virtualenv /your/env
 /your/env/pip install .
@@ -54,6 +58,7 @@ Matching supports wildcards (using the python [fnmatch module](https://docs.pyth
 Each section needs to contain a `target` entry pointing to the entry in the password store with the password (and optionally username) to use.
 
 Example:
+
 ```ini
 [github.com*]
 target=dev/github
@@ -63,58 +68,74 @@ target=dev/fooo-bar
 ```
 
 To instruct git to use the helper, set the `credential.helper` configuration option of git to:
+
 ```
 /full/path/to/pass-git-helper
 ```
+
 In case you do not want to include a full path, a workaround using a shell fragment needs to be used, i.e.:
+
 ```
 !pass-git-helper $@
 ```
 
 The option can be set e.g. via:
+
 ```sh
 git config credential.helper '!pass-git-helper $@'
 ```
 
 If you want to match entries not only based on the host, but also based on the path on a host, set `credential.useHttpPath` to `true` in your git config, e.g. via:
+
 ```sh
 git config credential.useHttpPath true
 ```
+
 Afterwards, entries can be matched against `host.com/path/to/repo` in the mapping.
 This means that in order to use a specific account for a certain github project, you can then use the following mapping pattern:
+
 ```ini
 [github.com/username/project*]
 target=dev/github
 ```
+
 Please note that when including the path in the mapping, the mapping expressions need to match against the whole path.
 As a consequence, in case you want to use the same account for all github projects, you need to make sure that a wildcard covers the path of the URL, as shown here:
+
 ```ini
 [github.com*]
 target=dev/github
 ```
+
 The host can be used as a variable to address a pass entry.
 This is especially helpful for wildcard matches:
+
 ```ini
 [*]
 target=git-logins/${host}
 ```
+
 The above configuration directive will lead to any host that did not match any previous section in the ini file to being looked up under the `git-logins` directory in your passwordstore.
 
 Using the `includeIf` directive available in git >= 2.13, it is also possible to perform matching based on the current working directory by invoking `pass-git-helper` with a conditional `MAPPING-FILE`.
 To achieve this, edit your `.gitconfig`, e.g. like this:
+
 ```ini
 [includeIf "gitdir:~/src/user1/"]
     path=~/.config/git/gitconfig_user1
 [includeIf "gitdir:~/src/user2/"]
     path=~/.config/git/gitconfig_user2
 ```
+
 With the following contents of `gitconfig_user1` (and `gitconfig_user2` repspectively), `mapping_user1.ini`, which could contain a `target` entry to e.g. `github.com/user1` would always be invoked in `~/src/user1`:
+
 ```ini
 [user]
     name = user1
 [credential]
     helper=/full/path/to/pass-git-helper -m /full/path/to/mapping_user1.ini
 ```
+
 See also the offical [documentation](https://git-scm.com/docs/git-config#_includes) for `.gitconfig`.  
 
 ### DEFAULT section
@@ -165,14 +186,16 @@ Extracts the data from a line indexed by its line number.
 Optionally a fixed-length prefix can be stripped before returning the line contents.
 
 Configuration:
+
 * `line_username`: Line number containing the username, **0-based**. Default: 1 (second line)
-* `skip_username`: Number of characters to skip at the beginning of the line, for instance to skip a `user: ` prefix. Similar to `skip_password`. Default: 0.
+* `skip_username`: Number of characters to skip at the beginning of the line, for instance to skip a `user:` prefix. Similar to `skip_password`. Default: 0.
 
 #### Strategy "regex_search"
 
 Searches for the first line that matches a provided regular expressions and returns the contents of that line that are captured in a regular expression capture group.
 
 Configuration:
+
 * `regex_username`: The regular expression to apply. Has to contain a single capture group for indicating the data to extract. Default: `^username: +(.*)$`.
 
 #### Strategy "entry_name"