Fix CI

.markdown-link-check.json

@@ -1,3 +1,2 @@
 {
-  "ignorePatterns": ["https://github.com/bergercookie/syncall/blob/master/readme-tw-caldav.md"]
 }

.pre-commit-config.yaml

@@ -26,7 +26,7 @@ repos:
     hooks:
       # https://github.com/tcort/markdown-link-check#config-file-format
       - id: markdown-link-check
-        args: ["--progress", "--config", ".markdown-link-check.json"]
+        args: ["--progress", "--config", ".markdown-link-check.json", "-q"]
   - repo: https://github.com/markdownlint/markdownlint
     rev: "v0.12.0"
     hooks:

docs/readme-fs-gkeep.md

@@ -96,7 +96,7 @@ Read more about this [here](https://gkeepapi.readthedocs.io/en/latest/#faq).
 
 To provide the password, you can either use the `GKEEP_USERNAME` and
 `GKEEP_PASSWD` before running `fs_gkeep_sync` or (recommended), use [the UNIX
-Password Manager](https://www.passwordstore.org/) to store your username and
+Password Manager](https://wiki.archlinux.org/title/Pass) to store your username and
 password to your Google account and provide the paths to them (use
 `--user-pass-path ... --passwd-pass-path ...` in this case).
 

docs/readme-tw-asana.md

@@ -32,13 +32,13 @@ above
 
 First, generate a [personal access token](https://developers.asana.com/docs/personal-access-token)on Asana.
 
-| ![1](misc/asana/authentication/1.png) | ![2](misc/asana/authentication/2.png) | ![3](misc/asana/authentication/3.png) |
-| :-----------------------------------: | :-----------------------------------: | :-----------------------------------: |
+| ![1](../misc/asana/authentication/1.png) | ![2](../misc/asana/authentication/2.png) | ![3](../misc/asana/authentication/3.png) |
+| :--------------------------------------: | :--------------------------------------: | :--------------------------------------: |
 
 Next, make this token available to `tw_sync_asana`. This can be done by either:
 
 - Storing the token in environment variable `ASANA_PERSONAL_ACCESS_TOKEN`.
-- Storing the token with [password store](https://www.passwordstore.org/),
+- Storing the token with [password store](https://wiki.archlinux.org/title/Pass),
   and telling Asana to load the token with `--token-pass-path`.
 
 ### Find IDs of available workspace
@@ -69,7 +69,7 @@ tw_asana_sync --taskwarrior-tags asana --asana-workspace-name my-workspace --tok
 ### Pass the Access Token via environment variable
 
 If you haven't installed or don't want to install [password
-store](https://www.passwordstore.org/) you can pass the access token via an
+store](https://wiki.archlinux.org/title/Pass) you can pass the access token via an
 environment variable
 
 ```sh

docs/readme-tw-caldav.md

@@ -10,7 +10,7 @@ program keep synchronized, the following attributes (tw entries will be converte
 
 ## Demo - first run - populating tasklist in Nextcloud
 
-![demo_gif](misc/tw_caldav_sync.gif)
+![demo_gif](../misc/tw_caldav_sync.gif)
 
 ### Mappings
 
@@ -64,7 +64,7 @@ In order to successfully run a sync, you will need the following flags set (mand
 - `--caldav-url`: URL where the caldav calendar is hosted at (including `/dav` if applicable)
 - `--caldav-user`: Username required to authenticate your caldav instance
   - Can also be provided via the `CALDAV_USERNAME` environment variable
-- `--caldav-passwd`, `--caldav-passwd-pass-path`: Path to your password `.gpg` file in your [password store](https://www.passwordstore.org/)
+- `--caldav-passwd`, `--caldav-passwd-pass-path`: Path to your password `.gpg` file in your [password store](https://wiki.archlinux.org/title/Pass)
   - Alternatively, the password can be provided directly via the `CALDAV_PASSWD` environment variable
 
 The following flag is optional:

docs/readme-tw-gcal.md

@@ -15,7 +15,7 @@ addition/modification/deletion events between them.
 
 ## Demo - first run - populating calendar in GCal
 
-![demo_gif](misc/demo.gif)
+![demo_gif](../misc/demo.gif)
 
 ## Motivation
 
@@ -56,7 +56,7 @@ and download the credentials:
   as shown below. This is the file you need to point to when running
   `tw_gcal_sync`.
 
-  ![download-btn](misc/gcal-json-btn.png)
+  ![download-btn](../misc/gcal-json-btn.png)
 
 To specify your custom credentials JSON file use the `--google-secret` flag as follows:
 

docs/readme-tw-gkeep.md

@@ -51,7 +51,7 @@ Read more about this [here](https://gkeepapi.readthedocs.io/en/latest/#faq).
 
 To provide the password, you can either use the `GKEEP_USERNAME` and
 `GKEEP_PASSWD` before running `tw_gkeep_sync` or (recommended), use [the UNIX
-Password Manager](https://www.passwordstore.org/) to store your username and
+Password Manager](https://wiki.archlinux.org/title/Pass) to store your username and
 password to your Google account and provide the paths to them (use
 `--user-pass-path ... --passwd-pass-path ...` in this case).
 

docs/readme-tw-gtasks.md

@@ -1,6 +1,6 @@
 # [Taskwarrior](https://taskwarrior.org/) ⬄ [Google Tasks](https://support.google.com/tasks/answer/7675772)
 
-![logo](misc/meme-tw-gtasks.png)
+![logo](../misc/meme-tw-gtasks.png)
 
 ## Description
 
@@ -10,7 +10,7 @@ modification / deletion events between them.
 
 ## Demo - populating a list in Google Tasks (view from Google Calendar)
 
-![demo_gif](misc/tw_gtasks_sync.gif)
+![demo_gif](../misc/tw_gtasks_sync.gif)
 
 ## Motivation
 
@@ -73,7 +73,7 @@ that will be reused if found by the app.
 
 For creating your own Google Cloud Developer App:
 
-- Go to the [Google Cloud developer console](tw-gtasks-integration-test)
+- Go to the [Google Cloud developer console](https://console.cloud.google.com/)
 - Make a new project
 - From the sidebar go to `API & Services` and once there click the `ENABLE APIS AND SERVICES` button
 - Look for and Enable the `Tasks API`
@@ -94,7 +94,7 @@ and download the credentials:
   as shown below. This is the file you need to point to when running
   `tw_gtasks_sync`.
 
-  ![download-btn](misc/gcal-json-btn.png)
+  ![download-btn](../misc/gcal-json-btn.png)
 
 To specify your custom credentials JSON file use the `--google-secret` flag as follows:
 

docs/readme-tw-notion.md

@@ -56,7 +56,7 @@ sync from the URL and paste it when running the `tw_notion_sync` script.
 There are two ways `tw_notion_sync` can read the aforementioned API token:
 
 - Via the `NOTION_API_KEY` environment variable or,
-- Via the [UNIX Password Manager](https://www.passwordstore.org/). You can
+- Via the [UNIX Password Manager](https://wiki.archlinux.org/title/Pass). You can
   specify the path in the Pass manager to read the encrypted token from. The
   default path is `notion.so/dev/integration/taskwarrior/token` under the
   password store.