Update workflow with new actions versions and add troubleshooting instructions.

.github/workflows/actions.yml

@@ -10,10 +10,10 @@ jobs:
     steps:
 
       - name: checkout repo content
-        uses: actions/checkout@v2 # checkout the repository content to github runner
+        uses: actions/checkout@v4 # checkout the repository content to github runner
 
       - name: setup python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: '3.9' # install the python version needed
 
@@ -35,7 +35,7 @@ jobs:
           git diff-index --quiet HEAD || (git commit -a -m "updated logs" --allow-empty)
 
       - name: push changes
-        uses: ad-m/github-push-action@v0.6.0
+        uses: ad-m/github-push-action@master
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           branch: main 

README.md

@@ -10,3 +10,13 @@ This example shows how to run a Python script as cron job with GitHub Actions. I
 - Inspect and configure cron job in GitHub Action `.github/workflows/actions.yml`
 - It can install and use third party packages from `requirements.txt`
 - Secret environment variables can be used. Set secrets in Settings/Secrets/Actions -> 'New repository secret'. Use the same secret name inside `actions.yml` and `main.py`
+
+# Actions failing because of Node issues while running GitHub workflow or other issues
+
+- In case a step of the workflow fails because of Node-related issue, you need to update the version of the actions you use to the most recent ones. Check out the actions repositories:
+
+1. [actions/checkout](https://github.com/actions/checkout)
+2. [actions/setup-python](https://github.com/actions/setup-python)
+3. [ad-m/github-push-action](https://github.com/ad-m/github-push-action)
+
+- Should the push action fail because of a permission error like `remote: Write access to repository not granted.`, grant the remote write access from your repository under `Settings -> Actions -> General -> Workflow permissions."