README: suggest release instead of branch name

README.md

@@ -11,7 +11,9 @@ An example GitHub Action workflow using this action would look like the followin
 ```yaml
 name: update-flake-lock
 on:
-  workflow_dispatch:
+  workflow_dispatch: # allows manual triggering
+  schedule:
+    - cron: '0 0 * * *' # runs daily at 00:00
 
 jobs:
   lockfile:
@@ -20,7 +22,6 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v2
       - name: Update flake.lock
-        uses: DeterminateSystems/update-flake-lock@main
+        uses: DeterminateSystems/update-flake-lock@v1
 ```
 
-To have this workflow run on a recurring basis, see the [GitHub Actions documentation on the `schedule` key](https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#schedule).

action.yml

@@ -15,10 +15,23 @@ runs:
         GIT_AUTHOR_EMAIL: <github-actions[bot]@users.noreply.github.com>
         GIT_COMMITTER_NAME: github-actions[bot]
         GIT_COMMITTER_EMAIL: <github-actions[bot]@users.noreply.github.com>
+    - run: |
+        content="$(git log --format=%b -n 1)"
+        content="${content//'%'/'%25'}"
+        content="${content//$'\n'/'%0A'}"
+        content="${content//$'\r'/'%0D'}"
+        echo "::set-output name=msg::$content"
+      shell: bash
+      id: commit_message
     - name: Create PR
       uses: peter-evans/create-pull-request@v3
       with:
         branch: update_flake_lock_action
         delete-branch: true
         title: "flake.lock: Update"
-        body: Automated changes by the [update-flake-lock](https://github.com/DeterminateSystems/update-flake-lock) GitHub Action.
+        body: |
+          Automated changes by the [update-flake-lock](https://github.com/DeterminateSystems/update-flake-lock) GitHub Action.
+
+          ```
+          ${{ steps.commit_message.outputs.msg }}
+          ```