docs: CONTRIBUTING-Staging.MD: Update staging instructions

Add PAT_FOR_ISSUES handling and reset instructions.

Author: neural-loop

CONTRIBUTING-Staging.MD

@@ -12,13 +12,14 @@ The process involves using a dedicated `staging` branch on your personal fork of
 
 Before your fork can deploy a staging site, you must enable GitHub Pages and set the build source to GitHub Actions. You only need to do this once per fork.
 
-![img.png](static/images/img.png)
-
 1.  Navigate to your forked repository on GitHub.
 2.  Go to the **Settings** tab.
 3.  In the left sidebar, click on **Pages**.
 4.  Under the **Build and deployment** section, select **GitHub Actions** from the **Source** dropdown menu. The configuration will be handled automatically by the workflow file in the repository.
 
+![img.png](static/images/img.png)
+
+
 #### Step 2: Create a Local `staging` Branch
 
 If you don't already have one, create a local `staging` branch. It's best to base this off the latest version of the main repository's `main` branch.
@@ -53,25 +54,42 @@ git push origin staging
 
 Pushing to the `staging` branch triggers the `Deploy Hugo site to Pages` GitHub Action. Once the action completes, your staging site will be live. You can find the URL in your fork's repository settings on the same **Settings > Pages** screen you configured in Step 1.
 
+## Handling the `PAT_FOR_ISSUES` Secret
+
+Our GitHub Actions workflow includes a step to automatically update the "Mission Board" by fetching open issues from project repositories. This step requires a secret key called `PAT_FOR_ISSUES` (a Personal Access Token).
+
+Since forks do not have this secret, the **"Update Mission Board" step will fail, causing the entire build to stop.** This will prevent your staging site from deploying.
+
+**To fix this**, you can simply tell the workflow to continue even if this specific step fails. Add `continue-on-error: true` to the "Update Mission Board" step in the `.github/workflows/main.yml` file within your `staging` branch.
+
+```yaml
+      - name: Update Mission Board
+        env:
+          PAT_FOR_ISSUES: ${{ secrets.PAT_FOR_ISSUES }}
+        run: npm run update-mission-board
+        continue-on-error: true # Add this line
+```
+
+This change ensures that a failure in fetching issues won't block the deployment of your staging site. The Mission Board page on your preview site may not have the latest issues, but the rest of the site will build and deploy correctly.
+
 ## Resetting Your Staging Branch
 
-Sometimes, you may need to start fresh with a new staging environment, especially if your previous staging branch contains changes you no longer need or if it has diverged significantly from the main project.
+Sometimes, you may need to start fresh with a new staging environment.
 
 1.  **Delete the Remote `staging` Branch:**
     ```bash
     git push origin --delete staging
     ```
 
 2.  **Recreate the Branch Locally:**
-    Delete your local `staging` branch, then create a new one based on the latest `upstream/main`.
     ```bash
     git branch -D staging
     git fetch upstream
     git checkout -b staging upstream/main
     ```
 
 3.  **Merge New Features and Push:**
-    You can now merge your new feature branches into this clean `staging` branch and push to your fork as described in the workflow above. A `force push` might be necessary if you are overwriting an existing branch with a different history.
+    You can now merge your new feature branches and push to your fork. A `force push` might be necessary if you are overwriting an existing branch with a different history.
     ```bash
     git push origin staging --force
     ```