Added GH workflow

Author: ginobuzz

.github/workflows/deploy.yml

@@ -0,0 +1,50 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+# Allow one concurrent deploy; cancel in-progress runs when a new push lands.
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - name: Build
+        # Derive Vite's base from the repo name so the site loads correctly at
+        # https://<user>.github.io/<repo>/ without hardcoding the name anywhere.
+        run: |
+          REPO_NAME="${GITHUB_REPOSITORY#*/}"
+          VITE_BASE="/$REPO_NAME/" npm run build
+
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

vite.config.js

@@ -2,7 +2,11 @@ import { defineConfig } from 'vite'
 import react from '@vitejs/plugin-react'
 
 // https://vite.dev/config/
+//
+// `base` must match the path the site is served from. On GitHub Pages that's
+// `/<repo-name>/`. The Pages deploy workflow sets VITE_BASE to the correct
+// value so renames of the repo don't silently break asset URLs.
 export default defineConfig(({ command }) => ({
   plugins: [react()],
-  base: command === 'build' ? '/Teams-TargetedMessages-v3/' : '/',
+  base: command === 'build' ? (process.env.VITE_BASE || '/teams-shell/') : '/',
 }))