syntaqxA repository's pages fail one card at a time: each page still fails on what it is about (the pull request, the issue, the commit, the run, the file, the list), and every other read goes through part(), so a service that does not answer leaves Unavailable in that card's place, not a blank card or a crashed page. Pull request: the diff, Sessions, Decisions, What happened, the preview, the merge queue's findings, Labels, Milestone, Notifications and the reviewer and assignee pickers each say so in place (settings stay strict: unread, they would let checks be ignored). Issue: Labels, Milestone, Notifications, assignees, links from outside g1t, Work and Decisions. Commit: its pull request (a stream that could reject into an Await with no errorElement), comments and the issues it closed. Code, tree and file: branches (inside the branch menu), deployments, the fork's source, the About sidebar (Packages no longer says "No packages published" when it could not be read) and a file's CODEOWNERS check; environmentsFor and forkSourceFor no longer swallow failures. Actions: workflows; a run's artifacts and job summaries; a check run's annotations. Deployments: environments, history and g1t.page hosting each on their own, never "No deployments yet" or "members can turn on hosting" because of a failure; a deployment that cannot be read is a 503, not a 404. Work: Live now, the queue, What happened, Just landed. Lists: label and milestone filters, branch rows' pull requests and previews, activity (no longer "No activity yet"), fork descriptions, compare's branches and changes, new pull request's forks and a named fork. Overview: Needs you, deployments, observability. Boundaries around the README, About, the run graph, annotations, summaries, report cards and the sidebar boxes. Kept quiet on purpose, each a decoration or an extra the service checks again: teams for mentions, ended claims, merge choices (settings answer), job-by-job checks, watcher and tag counts, the star count, release suggestions, compute notes, the plan on Deployments. Checked: apps/web tsc -b; npm test (987, 1 skipped).74236deHistory
- ..
- 0001_init.sql
- 0002_text_ids.sql
- 0003_unique_email.sql
- 0004_email_verification.sql
- 0005_token_expiry.sql
- 0006_device_codes.sql
- 0007_rfc3339_timestamps.sql
- 0008_workspaces.sql
- 0009_oauth.sql
- 0010_workspace_tokens.sql
- 0011_agent_tokens.sql
- 0012_avatars.sql
- 0013_profiles.sql
- 0014_workspace_redirects.sql
- 0015_run_credentials.sql
- 0016_deleted_workspaces.sql
- 0017_github.sql
- 0018_invites.sql
- 0019_user_emails.sql
- 0020_access.sql
- 0021_waitlist_notices.sql
- 0022_token_scopes.sql
- 0023_retire_token_reach.sql
- 0024_g1t_name.sql
- 0025_workspace_soft_delete.sql
- 0026_workspace_residency.sql
- 0027_teams.sql
- 0028_team_creation.sql
- 0029_workspace_aliases.sql
- 0030_job_tokens.sql
- 0031_membership.sql
- 0032_two_factor.sql
- 0033_identity_jobs.sql
- 0034_fine_grained_tokens.sql
- 0035_deploy_keys.sql
- 0036_email_confirmation_codes.sql
- 0037_account_deletion.sql
- 0038_shared_invites.sql
- 0039_profile_timezone.sql
- 0040_workspace_invitations.sql
- 0041_one_kind_of_token.sql
- 0042_username_case.sql
- 0043_website_tokens.sql
- 0044_dock_pins.sql
- 0045_people_and_teams.sql
- 0046_sound_settings.sql
- 0047_suspension.sql
- 0048_ask_tokens.sql
- 0049_privacy.sql
- 0050_onboarding.sql