syntaqxOne tab pings, once, and only for what is for you. Every open tab of g1t heard the same arrival, so each played its sound and showed its desktop toast; now a tab claims the arrival across the browser before pinging (lib/one-tab.ts: a Web Lock held while a ten-minute mark is written to the localStorage every tab shares, so a tab that comes second finds the mark), a tab in front claims at once and the others wait 400 ms, so the one you are looking at is the one that pings, and the sound and the toast for an arrival go together. A message heard over both the conversation's socket and the feed is claimed once, by its id. g1t's answer no longer pings as it starts: it arrives empty and thinking the moment a question is asked, which pinged right after your own message; it now pings once, when it is written. Where Web Locks or storage are missing, every tab pings as before. Checked: the site's typecheck and its 893 tests (new: the claim's rule and the answer's silence until it is written), and a production build whose chunks load first without error.d87be0cHistory
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml