syntaqxNotifications settle themselves once nothing is left to do, and Home's Needs you shows your pull requests that are ready to merge or need you. Live today, Home's "From your notifications" and `g1t status` still listed "Deploy failed on main" (Run 327) and "CI failed on main" (Run 243) hours after later runs on main passed, "Reviews asked of you" listed flagon-io/g1t#39 after it merged, flagon-io/automation-lab#38 told its author "turned off auto-merge: It joined the merge queue" though the queue then merged it, and Needs you said 0 while #41 (CI passed, no approvals required) waited only for its author to merge it. The inbox only ever closed three things by itself (an agent's stall when it went on, a removed review request, an answered invitation); everything else stayed unread until marked by hand. Now the events service settles an item (marks it done and read, so it leaves the unread count, the bell, Needs you and `g1t status`, and stays in Done with its history) when the event that ends it arrives (services/events/src/inbox.rs, "Settling"): a workflow's failures on a branch when that workflow next passes there; a pull request's failed checks when checks.completed passes on its head; a deployment's failure when that production or preview deploys; a deployment waiting for review when its run ends; a review request when it is removed from you or your team; a token approval when an owner decides it; a bypass request when it is decided; your own item on a thread when you comment or review there; and everything about an issue or pull request, its previews included, once it merges or closes. A merge or close still reaches each thread's history but settles it at once, so nobody is pushed a notification that is already done. Two kinds are gone: "is live again" after a failed deployment (it settles the failure instead; watchers who chose deployments still hear of every deployment) and auto-merge turned off because the pull request joined the merge queue (work's pull.auto_merge_disabled now says `queued`, and the inbox tells nobody). Migration 0011 settles, once, items written before this whose cause the event log shows is over: run failures passed since, deployment failures deployed since, threads of issues and pull requests merged or closed since, and the merge-queue auto-merge notices. Each settled person's live count is told again. On the work side, every open pull request's remembered lifecycle is now shown in lists (list_active_pulls), not only those g1t's agent made: advance, which the runner calls on every event that can move one, remembers it for pull requests with auto-merge on too and reads whether one is behind as stored with its mergeability rather than asking repos (g1t's own still ask, since it merges them); after a merge, managed_pulls for that repository includes every open one with a remembered lifecycle; a settings or ruleset change forgets the repository's remembered lifecycles, so each is worked out again on its next showing. Home and Code's Overview turn your pull request's lifecycle into rows in the workspace: needs_you as Resolve (a conflict) or Decide, and ready as "Ready to land when you merge it." with Merge, a Ready to merge chip and its required checks shown passing. The notifications guide has a section on threads that settle themselves; the Home, pull requests (auto-merge) and webhooks guides say what changed. Checked: cargo test -p g1t-events (64, 7 of them new, for the settling rules), -p g1t-work (189), -p g1t-contracts (312), -p g1t-api the_docs_copy_is_current; clippy adds no warning; the site's tsc -b --force and unit tests (934); the docs build; migration 0011 against sample rows in SQLite.10396abHistory
README.md
g1t/detect
Says what a g1t.page build of the checkout would find, without building or deploying anything: the same rules g1t/deploy builds with.
steps:
- uses: actions/checkout@v5
- id: detect
uses: g1t/detect@v1
- if: steps.detect.outputs.kind == 'none'
run: echo "::error::Nothing here would be served."
- if: steps.detect.outputs.framework == 'hugo'
run: echo "A Hugo site, served from ${{ steps.detect.outputs.output-dir }}"
- if: steps.detect.outputs.install != ''
run: ${{ steps.detect.outputs.install }}yaml
Inputs
| Input | Default | |
|---|---|---|
root-dir | The checkout | Where the project is in the checkout. |
build-command | None | A build command of your own, as g1t/deploy takes it. |
output-dir | None | An output folder of your own, as g1t/deploy takes it. |
build-as | auto | What it is built as: auto, static, workers or docker (Container), as g1t/deploy takes it. |
dockerfile | None | A Dockerfile's path of your own, as g1t/deploy takes it. |
Outputs
| Output | |
|---|---|
kind | workers (a wrangler.jsonc, wrangler.json or wrangler.toml, a framework's Cloudflare adapter, or a Node.js server run as a Worker), static (a site a build writes), html (the files as they are), container (a server that is not run as a Worker, a framework set up to need a server, or a Dockerfile with nothing else to serve) or none (nothing to serve). |
framework | The framework it is built with, from the table below; node for a Node.js server run as a Worker; for a container without one, dockerfile, or the server g1t writes a Dockerfile for (node, django, flask, fastapi, python, go, rails, rack, laravel, php). Empty when there is none. |
dockerfile | A container's own Dockerfile, relative to the project. Empty when g1t writes one, and for anything that is not a container. |
port | The port a container listens on: its Dockerfile's EXPOSE, else 8080. |
entry | For a Node.js server run as a Worker, the file that starts it, relative to the project. Empty for anything else. |
install | How dependencies are installed, from the lockfile: npm ci, pnpm install --frozen-lockfile, and so on, and bundle install for Jekyll. Empty when there is nothing to install. |
build | What builds it: your command, the package's build script (npm run build), the framework's own command, or wrangler deploy --dry-run for Workers. Empty when nothing does. |
output-dir | The folder served, relative to the project (. for the project itself): yours, a Workers project's assets directory, the folder the framework writes, or the first of dist, build, out, public, _site, .output/public that exists. Empty when a build has yet to write it, as for a Cloudflare adapter's Worker. |
When kind is none, the step's log says what to change or add, such as
a Dockerfile. Docker deployments
has the order in which a project's kind is decided.
Frameworks
framework | Found by | Serves |
|---|---|---|
vite, vite-react, vite-vue, vite-svelte, vite-solid, vite-preact | vite, and the framework's Vite plugin | dist, or build.outDir |
astro | astro | dist, or outDir; a Worker with @astrojs/cloudflare |
nextjs | next | out with output: 'export'; a Worker with @opennextjs/cloudflare and a wrangler.jsonc |
sveltekit | @sveltejs/kit | build with adapter-static; a Worker with adapter-cloudflare |
nuxt | nuxt | .output/public, from nuxi generate |
react-router, remix | @react-router/dev, @remix-run/dev | build/client with ssr: false |
gatsby | gatsby | public |
docusaurus | @docusaurus/core | build |
eleventy | @11ty/eleventy | _site |
angular | @angular/core and angular.json | dist/<project>/browser |
create-react-app | react-scripts | build |
hugo | hugo.toml, or Hugo's config.toml | public |
jekyll | _config.yml and a Gemfile | _site |
mdbook | book.toml | book |
What deploys has
each one's build command. Your build-command and output-dir win over
what is detected.
It runs g1t-runner detect, found or downloaded as g1t/deploy finds it.