From c47fc6fc84d6e49afddfc8149d8a5f83f64663c4 Mon Sep 17 00:00:00 2001
From: Dave Gallant <davegallant@gmail.com>
Date: Sat, 9 Dec 2023 00:26:31 -0500
Subject: [PATCH] Update README.md

---
 README.md | 23 ++++++-----------------
 1 file changed, 6 insertions(+), 17 deletions(-)

diff --git a/README.md b/README.md
index b983023..5fb958d 100644
--- a/README.md
+++ b/README.md
@@ -46,8 +46,6 @@ expressions:
 
 ## Github Actions
 
-> Commiting the pickled data (previous_matches) back into the repository is a bit of a hack, but allows for a simpler setup.
-
 An action can be setup to scan for deals, send a notification and store previously found deals in the repo.
 
 It also requires the corresponding [encrypted secrets](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets) setup.
@@ -56,35 +54,26 @@ It also requires the corresponding [encrypted secrets](https://docs.github.com/e
 # .github/workflows/rfd-notify.yml
 
 on:
+  push:
   schedule:
     - cron: "*5 * * * *"
 jobs:
   rfd_notify:
-    runs-on: ubuntu-latest
     name: rfd-notify
     steps:
       - name: Checkout
         uses: actions/checkout@v3
         with:
           fetch-depth: 0
-
+      - uses: actions/cache@v3
+        id: cache
+        with:
+          path: previous_matches
+          key: previous_matches
       - name: Run rfd-notify
         uses: davegallant/rfd-notify@main
         env:
           APPRISE_URL: ${{ secrets.APPRISE_URL }}
-
-      - name: Commit files
-        run: |
-          git config --local user.email "action@github.com"
-          git config --local user.name "RFD Notify"
-          git add previous_matches
-          git commit -m "Update previous_matches" -a || true
-
-      - name: Push changes
-        uses: ad-m/github-push-action@master
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          branch: ${{ github.ref }}
 ```
 
 ## Gitlab Pipelines