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_lifecycle.sql
- 0003_repo_settings.sql
- 0004_up_to_date.sql
- 0005_assignees.sql
- 0006_merge_rules.sql
- 0007_timeline.sql
- 0008_plans.sql
- 0009_lifecycle_snapshot.sql
- 0010_merge_queue.sql
- 0011_agent_messages.sql
- 0012_exchanges.sql
- 0013_commit_statuses.sql
- 0014_mergeability.sql
- 0015_agent_runs_and_memory.sql
- 0016_by_author.sql
- 0017_agent_mentions.sql
- 0018_guardrails.sql
- 0019_memory_capture.sql
- 0020_agent_waits.sql
- 0021_confidence.sql
- 0022_required_checks.sql
- 0023_read_paths.sql
- 0024_g1t_name.sql
- 0025_requested_by.sql
- 0026_code_owners.sql
- 0027_labels_milestones_bases.sql
- 0028_rulesets.sql
- 0029_commit_checks.sql
- 0030_comment_edits.sql
- 0031_mention_revisions.sql
- 0032_contributions.sql
- 0033_agent_comments.sql