Connecting GitHub to a workspace is one click and one trip to GitHub. A workspace owner's Connect GitHub on Import from GitHub links their GitHub account on the way if it is not linked yet and comes straight back to carry on: an installation they already have on GitHub and the workspace lacks is added rather than installed again (with several, they choose), and only with none are they sent to install the app; GitHub then returns them to the import page with the account connected. Before, linking and installing were separate chores (link, come back, install), Settings -> GitHub stopped at "Linked" with nowhere to go, and an app already on the account was "installed" again through GitHub's settings page. When GitHub returns after an installation that did not start from g1t, an unlinked account is linked on the way instead of showing an error with a button, and someone who owns one workspace has it added there without being asked which. Choose repositories on GitHub opens in the same tab, since GitHub brings you back after saving; Add a GitHub account still always installs on another account; Settings -> GitHub points to Import from GitHub once linked. A link that does not take shows the page instead of going round again. The GitHub guide describes the one-step flow. (The app's Setup URL was empty on GitHub, which left people there after installing; it is now set to /integrations/github/setup.) Checked: the site's typecheck (tsc -b --force), its 911 tests (new: what Connect GitHub does next), a production build and the deploy tool's 92 tests. #307 · 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		be0e43b	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		be0e43b	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	be0e43b	6 changed files (apps/web/app/lib/github.test.ts)
sudo	front		be0e43b	nothing it is built from changed
docs	front	deploy	be0e43b	1 changed file (apps/docs/src/content/docs/guides/github.md)

flagon-io/g1t

Deploy plan for c28ae41