Run pre-commit fix up (brisbanesocialchess#350)

* Run pre-commit fix up

* Update docs/minutes.html

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Author: jbampton

.github/workflows/pr-deploy-preview.yml

@@ -25,9 +25,9 @@ jobs:
         id: check_pelicanconf
         run: |
           if [ -f pelicanconf.py ]; then
-            echo "file_exists=true" >> $GITHUB_OUTPUT
+            echo "file_exists=true" >> "$GITHUB_OUTPUT"
           else
-            echo "file_exists=false" >> $GITHUB_OUTPUT
+            echo "file_exists=false" >> "$GITHUB_OUTPUT"
           fi
 
       - name: Install dependencies

README.md

@@ -28,6 +28,7 @@ Welcome to the source code repository for the Brisbane Social Chess website.
   - [Run Tests](#run-tests)
 - [About Brisbane Social Chess](#about-brisbane-social-chess)
 - [Getting Started / Building the Site](#getting-started--building-the-site)
+- [Build the Docker image for running `pre-commit` easily](#build-the-docker-image-for-running-pre-commit-easily)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 

docs/minutes.html

@@ -203,7 +203,7 @@ <h3>June 2024 – Committee Meeting (24/06/2025)</h3>
               <li>
                 Steve: AGM first steps
                 <br>
-                Steve suggested that we should start preparation for this year's AGM. First steps could be to choose a date and prepare a Notice of Meeting. Rob noted the need to include a financial report in the Notice so that this can be approved at the AGM.  This then requires that annual accounts are completed before the Notice can be submitted. Rob also noted that the Notice must include any resolutions to be considered and could include, for example, committee size. General discussion noted the desirability of including some reporting of BSC committee activity over the last year in the Notice such as some commentary from the President or an indiaction of how many committee meetings and resolutions were had during the year.  
+                Steve suggested that we should start preparation for this year's AGM. First steps could be to choose a date and prepare a Notice of Meeting. Rob noted the need to include a financial report in the Notice so that this can be approved at the AGM.  This then requires that annual accounts are completed before the Notice can be submitted. Rob also noted that the Notice must include any resolutions to be considered and could include, for example, committee size. General discussion noted the desirability of including some reporting of BSC committee activity over the last year in the Notice such as some commentary from the President or an indication of how many committee meetings and resolutions were had during the year.
                 <br>
                 A tentative date for the AGM of Sunday the 31st August 2025 was agreed. Matt will collect the necessary documentation and Rob will prepare the annual financial report when this is done. Steve will draft a Notice of Meeting for committee consideration.
               </li>

packages/cfsite/test/index.spec.js

@@ -49,12 +49,12 @@ describe('API endpoints', () => {
 
 	it('handles user registration', async () => {
 		const body = JSON.stringify({
-			fname: 'Max',
-			lname: 'Base',
 			birthyear: '1990',
-			gender: 'male',
 			discordusername: '',
 			email: 'maxbasecode@gmail.com',
+			fname: 'Max',
+			gender: 'male',
+			lname: 'Base',
 		});
 
 		const request = new Request(BASE_URL + '/api/register', {