ci: add pipeline to review PRs

Author: UlisesGascon

.github/workflows/ci.yml

@@ -0,0 +1,34 @@
+name: Pull Request Pipeline
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  build-and-test:
+    name: Build, Test, and Generate Unique Artifact
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: 22
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm test
+
+      - name: Build the project
+        run: npm run build
+
+      - name: Upload build artifact
+        uses: actions/upload-artifact@v3
+        with:
+          name: site-preview-pr-${{ github.event.pull_request.number }}
+          path: ./build

README.md

@@ -24,6 +24,31 @@ $ npm run build
 
 This command generates static content into the `build` directory and can be served using any static contents hosting service.
 
+### Reviewing Pull Requests
+
+This project uses GitHub Actions to automate building, testing, and generating a preview for pull requests. Here's how you can review pull requests effectively:
+
+1. **Open the Pull Request**:
+   - Navigate to the **Pull Requests** tab in the repository.
+   - Select the PR you want to review.
+
+2. **Access the Build Artifact**:
+   - Go to the **Actions** tab in the repository.
+   - Find the workflow run associated with the pull request (usually named `Pull Request Pipeline`).
+   - Scroll down to the **Artifacts** section and download the artifact named `site-preview-pr-<PR_NUMBER>` (e.g., `site-preview-pr-123`).
+
+3. **Preview the Changes**:
+   - Extract the downloaded artifact.
+   - Serve the files locally using a simple HTTP server. For example:
+     ```bash
+     npx http-server <extracted-folder-path> -p 8080
+     ```
+   - Open `http://localhost:8080` in your browser to review the changes.
+
+4. **Provide Feedback**:
+   - Leave comments or suggestions directly in the pull request under the **Files changed** tab.
+
+
 ### Deployment
 
 There is a [pipeline](.github/workflows/deploy.yml) that will deploy anytime that a new commit lands to `main` branch.