From f1f371f89928781004a1045b82ee15a3e77c8ed9 Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Wed, 15 Jul 2020 17:52:02 +0200 Subject: [PATCH] Emphesize the yabridgectl todo And force the CI to run, because merge commits apparently don't trigger it. https://github.community/t/why-does-a-merge-commit-not-trigger-an-on-push-workflow/16770 --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4428f7c4..9200c5b7 100644 --- a/README.md +++ b/README.md @@ -27,11 +27,11 @@ Please let me know if there are any issues with other VST hosts. ## Usage -TODO: Refactor these sections to refer to yabridgectl for most of the setup. If -you are reading this, then you can either follow the instructions below or you -can download a preview version of yabridgectl from the [automated +**TODO: Refactor these sections to refer to yabridgectl for most of the setup. +If you are reading this, then you can either follow the instructions below or +you can download a preview version of yabridgectl from the [automated builds](https://github.com/robbert-vdh/yabridge/actions?query=workflow%3A%22Automated+builds%22+branch%3Amaster) -page. +page.** You can either download a prebuilt version of yabridge through the GitHub [releases](https://github.com/robbert-vdh/yabridge/releases) section, or you can