syntaqxThe g1t command line does a forge's daily work now, for people at a terminal and for agents in a shell, not only g1t push. g1t auth login signs in by approving a code in the browser (the API's device sign-in), or takes a token on stdin with --with-token; the token goes in the system keychain (macOS Keychain, Windows Credential Manager, the Secret Service), or in config.json readable by its owner only when there is none, and G1T_TOKEN overrides both. auth status, logout, token and switch handle several accounts on several hosts, g1t.sh and self-hosted ones (--hostname, G1T_HOST; a new host is asked where its API is through /.well-known/g1t.json). auth setup-git makes g1t git's credential helper for the host, and g1t push takes the same signed-in token before docker's.6eed8a0History
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql