syntaqxA workspace alias resolves for Actions and for a token's reach, so g1t/deploy@v1 is flagon-io/deploy everywhere. uses: looks for an owner that is an alias (g1t for flagon-io) under its workspace's slug when nothing has the name as written, as the calling workspace sees it, and names what it finds by its own path; a g1t/ name answers ahead of GitHub only for a public repository and is never looked for on GitHub. The API decides a refused call again under the alias's workspace, so a token for flagon-io/deploy reaches it as g1t/deploy and nothing more. Actions release creates a missing g1t/<name> repository, public, through the API before pushing, and stops on a private one. The workspaces guide documents workspace aliases, and the actions guide g1t's own actions under the alias.efdeefdHistory
- ..
- 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