Update commit.md

Author: MichaelCurrin

recipes/ci-cd/github-actions/workflows/commit.md

@@ -18,9 +18,33 @@ When you might want to create and persist changes in CI:
     - Update table of contents.
 
 
-## Sample
+## Samples
 
-Using the Publish to GitHub Action
+### No action
+
+A simple way to commit any changes.
+
+- `main.yml`
+    ```yaml
+    steps:
+      - run: # Modify files...
+
+      - name: Check for modified files
+        id: git-check
+        run: echo ::set-output name=modified::$(if git diff-index --quiet HEAD --; then echo "false"; else echo "true"; fi)
+
+      - name: Push changes
+        if: steps.git-check.outputs.modified == 'true'
+        run: |
+          git config --global user.name 'Automated Publisher'
+          git config --global user.email 'actions@users.noreply.github.com'
+          git remote set-url origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}
+          git commit -am "Commit message..."
+          git push
+    ```
+
+
+### Use the Publish to GitHub action
 
 This uses an action maintained by GitHub - [actions/push-new-files-back-to-master](https://github.com/marketplace/actions/push-new-files-back-to-master).
 
@@ -34,15 +58,15 @@ This uses an action maintained by GitHub - [actions/push-new-files-back-to-maste
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
     ```
 
-If you don't want to commit to master, you can specify a branch in `env` like so:
+If you don't want to commit to `master`, you can specify a branch in `env` like so:
 
-```
+```yaml
 BRANCH_NAME: my-branch
 ```
 
 If you look at the code in the action, this is what is does (excluding validating variables and working with GitHub LFS).
 
-I've refactored it.
+I've refactored it below.
 
 - `entrypoint.sh`
     ```sh
@@ -65,7 +89,7 @@ I've refactored it.
     git push publisher ${BRANCH_NAME}
     ```
 
-### Notes on the shell script
+#### Notes on the shell script
 
 This action works on the root and doesn't let you target a build directory like `_site`. So this is not a good idea for GH Pages. Even if you switch from `master` to `gh-pages` and your `.md` files are gone, your unversioned files (cache and gems) won't be ignored properly and would be committed unnecessarily.