From b32dedc34a170843a970b025c3a56a2dee28b7a4 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Fri, 29 Aug 2025 19:27:48 +0000
Subject: [PATCH 1/2] This commit fixes an issue in the `release-on-tag.yml`
 workflow where the release title was being set to a literal command string
 instead of its output.

The previous method of using command substitution `$(...)` directly within an action's `with` block is not a reliable way to execute shell commands in GitHub Actions.

This fix corrects the issue by introducing a dedicated step (`Get Release Title`) to first run the `sed` command and then store its result in a step output variable. The subsequent `Create Release` step then references this output to set the release name. This is the standard and robust method for handling dynamic values in GitHub Actions.

This commit also ensures the `softprops/action-gh-release` action is updated to `v2` and that the `RELEASE_TITLE.txt` file does not contain a trailing newline.
---
 .github/workflows/release-on-tag.yml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/release-on-tag.yml b/.github/workflows/release-on-tag.yml
index 2843363..0f1d8e7 100644
--- a/.github/workflows/release-on-tag.yml
+++ b/.github/workflows/release-on-tag.yml
@@ -41,10 +41,14 @@ jobs:
             echo "EOF"
           } >> "$GITHUB_OUTPUT"
 
+      - name: Get Release Title
+        id: get_release_title
+        run: echo "title=$(sed "s/\${TAG}/${{ github.ref_name }}/g" .github/RELEASE_TITLE.txt)" >> $GITHUB_OUTPUT
+
       - name: Create Release
-        uses: softprops/action-gh-release@v1
+        uses: softprops/action-gh-release@v2
         with:
-          title: $(sed "s/\${TAG}/${{ github.ref_name }}/g" .github/RELEASE_TITLE.txt)
+          name: ${{ steps.get_release_title.outputs.title }}
           body: ${{ steps.generate_notes.outputs.FINAL_BODY }}
           tag_name: ${{ github.ref_name }}
           draft: false

From a35c2cda54518a6b361efae8bdd1227f54931b94 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Fri, 29 Aug 2025 19:33:16 +0000
Subject: [PATCH 2/2] This commit updates the main documentation index file
 (`docs/README.md`) to include links to the recently added documentation for
 Prettier and repository badges.

The following links have been added:
- A link to `docs/prettier.md`
- A link to `docs/badges.md`

This makes the new documentation discoverable from the main documentation page.
---
 docs/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/README.md b/docs/README.md
index aa01d8d..7277b48 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -11,4 +11,6 @@ This directory contains the documentation for the `base` project.
 - **[Deploying to Render.com](./render.md)**: Instructions for deploying the project to the Render.com platform.
 - **[Merging `base` Into an Existing Repository](./merging-base.md)**: A guide on how to incorporate `base` into an existing project.
 - **[Standard Repository Files](./standard-files.md)**: An explanation of the standard configuration files like `.gitignore`, `.editorconfig`, and `.gitattributes`.
+- **[Using Prettier](./prettier.md)**: A guide to installing and using Prettier for code formatting.
+- **[Repository Badges](./badges.md)**: An explanation of how to use and create repository badges.
 - **[Maintaining `base` as a Template Repository](./template-repo.md)**: A guide for maintainers of this template, outlining best practices and administrative steps.