Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
5 tasks
…low the merge order Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
5 tasks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
6 tasks
gitluis
pushed a commit
that referenced
this pull request
Nov 4, 2026
…int to #56 for the records Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
…the old finlens-* ones Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
.github/workflows/pages.yml. On every push tomaster(that is, after a merge), or when you run it by hand from the Actions tab, it publishes the app as static files to GitHub Pages. Pull requests never deploy, so opening this PR doesn't publish anything. The app itself doesn't change.index.html,js/andsamples/(about 500 KB).docs/,CLAUDE.md, tests and CI files stay in the repo but aren't served.app-state*.json,app-export-*,ai-analysis-*,ai-history-*), the olderfinlens-*ones, or anything underdata/.Version: v2.0.3 (renumbered from v2.0.2: the rename PR #58 takes v2.0.2 so it merges first).
Before merging (one-time setup)
https://gitluis.github.io, so another site there could read FinLens's browser data.gitluis.github.io/<repo name>/, and a rename after people use it moves them to a new origin with empty browser data.Custom domain setup (placeholders)
Replace the placeholders, then follow the steps in this order. GitHub asks for verification and the repo setting before DNS, so nobody else can claim the domain while DNS points at GitHub.
<DOMAIN>example.app<SUBDOMAIN>app→app.example.app<SITE>app.example.apporexample.app<USERNAME>gitluis<REPO>finlensBuy
<DOMAIN>(Cloudflare or Porkbun). Delete any default records the registrar adds (parking page,wwwredirect).Verify
<DOMAIN>on your account (profile, not repo): profile picture → Settings → Pages → Add a domain →<DOMAIN>. GitHub shows a TXT record; add it at your DNS host:_github-pages-challenge-<USERNAME>Check it with
dig _github-pages-challenge-<USERNAME>.<DOMAIN> +short TXT, then Verify. Keep this record forever. Verifying<DOMAIN>also covers<SUBDOMAIN>.<DOMAIN>.Set the domain on this repo: this repo → Settings → Pages → Custom domain →
<SITE>→ Save. (Never on a<USERNAME>.github.iouser-site repo, or every project site shares it.)Add the DNS record(s), depending on
<SITE>:A subdomain (
<SUBDOMAIN>.<DOMAIN>, recommended):<SUBDOMAIN><USERNAME>.github.ioThe root domain (
<DOMAIN>):@185.199.108.153@185.199.109.153@185.199.110.153@185.199.111.153@2606:50c0:8000::153@2606:50c0:8001::153@2606:50c0:8002::153@2606:50c0:8003::153<USERNAME>.github.iowithout the repo name, never to a*.pages.github.ioaddress.*.<DOMAIN>): they allow takeovers even with a verified domain.Wait for the check: back in this repo's Settings → Pages, the DNS check turns green. DNS can take up to 24 hours.
Enforce HTTPS (same page) once it's offered; that can take up to 24 hours too.
Check it:
https://<SITE>opens the app with a valid certificate, andhttps://<USERNAME>.github.io/<REPO>/redirects to it.With an Actions deploy, the domain lives in the repo setting, so no
CNAMEfile is needed in the repo. If the custom domain is ever removed, delete its DNS records right away (and keep the TXT one), so the name can't be claimed.Automated checks: earlier run, not re-run · commit not recorded
Moved unchanged from this PR's "Test results" comment on 2026-11-04; not re-run, so not in the new table format. Originally a description section titled "How it was tested".
/finlens/subpath, the way Pages serves a project site. The app booted with all 24 views registered, no page errors, no 404s, andsamples/loaded by relative path (as the AI Eval view does).data/), and let a clean site through.master, and the workflow only runs after merge.pull_requestdoesn't trigger it, so there's no Actions run on this PR.Manual QA steps (after merging)
index.html,.nojekyll,js/…andsamples/….Please check before merging
gitluis.github.iofirst)master, so only passing code gets deployedhttps://claude.ai/code/session_013Z8iBUNj6C627mxmm1CurV
Generated by Claude Code