A project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build. #310 · flagon-io/g1t

check: `actions/checkout` checks out from g1t.

check: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

plan: `actions/checkout` checks out from g1t.

plan: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

migrate: `actions/checkout` checks out from g1t.

migrate: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

migrate: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

core: `actions/checkout` checks out from g1t.

core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

edge: `actions/checkout` checks out from g1t.

edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

front: `actions/checkout` checks out from g1t.

front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

smoke: `actions/checkout` checks out from g1t.

unit	stage	action	live	why
events	core		be0e43b	nothing it is built from changed
identity	core		be0e43b	nothing it is built from changed
repos	core		be0e43b	nothing it is built from changed
work	core		be0e43b	nothing it is built from changed
search	core		be0e43b	nothing it is built from changed
projects	core		be0e43b	nothing it is built from changed
chat	core		fb1fa31	nothing it is built from changed
artifacts	core		be0e43b	nothing it is built from changed
telemetry	core		be0e43b	nothing it is built from changed
notify	core		be0e43b	nothing it is built from changed
billing	core		be0e43b	nothing it is built from changed
integrations	core		fb1fa31	nothing it is built from changed
webhooks	core		be0e43b	nothing it is built from changed
actions	core		be0e43b	nothing it is built from changed
packages	core		be0e43b	nothing it is built from changed
security	core		be0e43b	nothing it is built from changed
deployments	core		be0e43b	nothing it is built from changed
runner	core		be0e43b	nothing it is built from changed
og	core		be0e43b	nothing it is built from changed
api	edge		be0e43b	nothing it is built from changed
pages	edge		5879548	nothing it is built from changed
status	edge		be0e43b	nothing it is built from changed
web	front	deploy	60e8784	7 changed files (apps/web/app/routes/repo/deployment.tsx)
sudo	front		be0e43b	nothing it is built from changed
docs	front		60e8784	nothing it is built from changed

flagon-io/g1t

Deploy plan for 6cd780f