Master branch now follows zig master

It makes more sense to have the master branch follow zig master, and
then create versioned branches to backport bug fixes to if nessesary

3 files changed, 2 insertions, 8 deletions

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 08d791f..7f6e216 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -2,6 +2,8 @@ name: CI
 on:
   push:
   pull_request:
+  schedule:
+    - cron: '0 0 * * *'
 
 jobs:
   test:
diff --git a/README.md b/README.md
index d6ad7a0..d872965 100644
--- a/README.md
+++ b/README.md
@@ -2,10 +2,6 @@
 
 A simple and easy to use command line argument parser library for Zig.
 
-Looking for a version that works with `zig master`? The `zig-master` branch has
-you covered. It is maintained by people who live at head (not me) and is merged
-into master on every `zig` release.
-
 ## Features
 
 * Short arguments `-a`
diff --git a/example/README.md.template b/example/README.md.template
index 1848d03..127cd74 100644
--- a/example/README.md.template
+++ b/example/README.md.template
@@ -2,10 +2,6 @@
 
 A simple and easy to use command line argument parser library for Zig.
 
-Looking for a version that works with `zig master`? The `zig-master` branch has
-you covered. It is maintained by people who live at head (not me) and is merged
-into master on every `zig` release.
-
 ## Features
 
 * Short arguments `-a`