update workflow to pull from existing branch

.github/workflows/benchmarks.yml

@@ -37,7 +37,15 @@ jobs:
         run: |
           git config --local user.email "action@github.com"
           git config --local user.name "GitHub Action"
-          git checkout -b benchmark-results
+          
+          if git show-ref --quiet refs/remotes/origin/benchmark-results; then
+            git fetch origin benchmark-results
+            git checkout benchmark-results
+            git merge FETCH_HEAD
+          else
+            git checkout -b benchmark-results
+          fi
+
           git add .
-          git commit -m "Update benchmark results" -a || echo "No changes to commit"
-          git push origin benchmark-results
+          git commit -m "Update benchmark results" || echo "No changes to commit"
+          git push origin benchmark-results

apps/docs/pages/benchmarks.mdx

@@ -19,6 +19,8 @@ Here are the key hardware specifications of this machine:
 
 Efficient proof generation is crucial to the interaction design of applications, especially those that rely on frequent or time-sensitive zk-SNARK proofs. Faster proving times lead to more responsive applications and better user experience. However, it's important to note that proving time can be influenced by several factors, including computational resources, circuit sizes, and the complexity of the computation being proved. Importantly proving time efficiency requirements may vary per user, a sequencer may not need blazing fast proving time, but a wallet may require proving times to be fast given user experience requirements.
 
+**Note: The current proving time includes program compiling time.**
+
 The chart below visualizes the trend in proving times, allowing users to understand how updates or modifications to Herald have influenced proving efficiency over time.
 
 <div style={{ display: 'flex', justifyContent: 'center', padding: '40px 0' }}>