🤖 feat: What's new dialog

.github/workflows/ci.yml

@@ -6,21 +6,24 @@ on:
   pull_request:
     branches: [main]
 
+permissions:
+  contents: read
+
 jobs:
   ci:
     runs-on: ubuntu-latest
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
 
       - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
+        uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # v2
         with:
-          bun-version: latest
+          bun-version: 1.4.0
 
       - name: Install dependencies
-        run: bun install
+        run: bun install --frozen-lockfile
 
       - name: Check formatting
         run: bun run fmt:check

.gitignore

@@ -13,10 +13,6 @@
 # testing
 /coverage
 
-# next.js
-/.next/
-/out/
-
 # production
 /build
 
@@ -33,12 +29,8 @@ yarn-error.log*
 # env files (can opt-in for committing if needed)
 .env*
 
-# vercel
-.vercel
-
 # typescript
 *.tsbuildinfo
-next-env.d.ts
 
 dist/
 release/

AGENTS.md

@@ -1,6 +1,6 @@
-# pulldash
+# better pr
 
-Pulldash is the fastest way to review pull requests.
+better pr is the fastest way to review pull requests.
 
 ## Development
 
@@ -10,9 +10,13 @@ _NEVER_ use browser tools - they will not work with this project.
 
 ## Principles
 
-- Performance is P1. If things feel laggy or are not smooth, it is of the utmost importance to fix. Pulldash exists because GitHub's PR review is slow.
+- Performance is P1. If things feel laggy or are not smooth, it is of the utmost importance to fix. better pr exists because GitHub's PR review is slow.
 - Tests should primarily occur at the data-layer, and the frontend should mostly dummily render the data.
 
+## Changelog
+
+Any user-visible feature or change must add an entry (newest first) to `CHANGELOG` in `src/browser/lib/changelog.ts`. It powers the "What's new" dialog; users see a dot until they open it. Use a unique `id` like `YYYY-MM-DD-slug`.
+
 ## Testing
 
 Tests should be minimal, not conflict with each other, and not be race-prone.

README.md

@@ -1,62 +1,36 @@
-<h1>
-  <img src="src/browser/logo.svg" alt="pulldash logo" width="40" height="40" align="center">
-  Pulldash
-</h1>
+# better pr
 
-![GitHub Release](https://img.shields.io/github/v/release/coder/pulldash) ![GitHub License](https://img.shields.io/github/license/coder/pulldash) ![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/coder/pulldash/ci.yml)
+A fast, keyboard-driven PR review UI.
 
-Fast, filterable PR review. Entirely client-side.
+## Setup
 
-> [!WARNING]
-> Pulldash is WIP. Expect bugs.
+Requires [Bun](https://bun.sh).
 
-## Try It
-
-**Browser**: [pulldash.com](https://pulldash.com). Replace `github.com` with `pulldash.com` in any PR URL.
-
-**Desktop**: [Latest release](https://github.com/coder/pulldash/releases) for Linux, macOS, Windows.
-
-[![Example](./docs/screenshots/overview.png)](https://pulldash.com)
-
-## Features
-
-- **Custom filters**: Add repos and filter by review requests, authored PRs, or all activity.
-
-  ![Filtering PRs](./docs/screenshots/filtering.png)
-
-- **Keyboard-driven**: `j`/`k` to navigate files, arrows for lines, `c` to comment, `s` to submit.
-
-  ![Keybinds](./docs/screenshots/keybind-driven.png)
-
-- **Fast file search**: `Ctrl+K` to fuzzy-find across hundreds of changed files.
-
-  ![Search](./docs/screenshots/search.png)
-
-## Why
+```bash
+git clone git@github.com:tskimmett/pulldash.git better-pr
+cd better-pr
+bun install
+bun start
+```
 
-- GitHub's review UI is slow (especially for large diffs)
-- No central view to filter PRs you care about
-- AI tooling has produced more PRs than ever before—making a snappy review UI essential
+Open http://localhost:3002 (set `PORT` to change it). To update: `git pull && bun install && bun start`.
 
-## How It Works
+## Sign in
 
-GitHub's API supports [CORS](https://docs.github.com/en/rest/using-the-rest-api/using-cors-and-jsonp-to-make-cross-origin-requests), so Pulldash runs entirely client-side. No backend proxying your requests.
+Use a **personal access token**: GitHub → Settings → Developer settings. It needs `repo` scope. The token stays in your browser's `localStorage`.
 
-- **Web Worker pool**: Diff parsing and syntax highlighting run in workers sized to `navigator.hardwareConcurrency`. The main thread stays free for scrolling.
+For Cognito repositories, the PAT must also have SSO configured and authorized for the Cognito organization.
 
-- **Pre-computed navigation**: When a diff loads, we index all navigable lines. Arrow keys are O(1)—no DOM queries.
+## Semantic review (optional, experimental)
 
-- **External store**: State lives outside React ([`useSyncExternalStore`](https://react.dev/reference/react/useSyncExternalStore)). Focusing line 5000 doesn't re-render the file tree.
+This feature is experimental and the results are hit-or-miss. Treat the walkthrough as a rough starting point, not a reliable summary of the PR.
 
-- **Virtualized rendering**: Diffs, file lists, and the command palette only render visible rows.
+The AI walkthrough appears only if an agent is available on the machine running the server: Claude Code logged in (or `ANTHROPIC_API_KEY`), or Codex logged in (or `OPENAI_API_KEY`). Diffs are sent to the provider you pick.
 
-## Development
+## Deploy
 
-```bash
-bun install
-bun dev
-```
+`bun run deploy` builds the app and uploads `dist/browser` to an Azure Static Web App. It needs `az login` plus `AZURE_SUBSCRIPTION`, `SWA_RESOURCE_GROUP` and `SWA_APP_NAME` (Bun reads them from `.env`). The hosted build has no server, so semantic review is unavailable there.
 
 ## License
 
-[AGPL](./LICENSE)
+[AGPL-3.0](./LICENSE)