syntaqxAgents are told how a commit closes an issue: on flagon-io/g1t #47 the billing session pushed its work straight to main with commits ending "(#47)", which only links the issue, so #47 stayed open after it shipped and was closed by hand. The plugin's SessionStart and subagent context (TRAILER in hooks/g1t.mjs), the work-on-issue skill's Finish step, the system prompt of sessions on Claude Managed Agents (for a repository's first commit) and the MCP server's instructions now say that a pull request's merge closes its issue, and a commit pushed straight to the default branch closes one only when its message says Closes #N (Fixes, Resolves), never with a bare (#N); the MCP instructions add that issue close with commit closes one after the fact. The Claude Code plugin guide says so. Deploy: api and integrations; the plugin ships with its next release. Checked: node --test of plugins/claude-code/test (56), cargo test -p g1t-api mcp (5), cargo test -p g1t-integrations agent_sessions (11).047ae5fHistory
- ..
- 0001_init.sql
- 0002_rfc3339_timestamps.sql
- 0003_protection.sql
- 0004_store_key.sql
- 0005_topics.sql
- 0006_stored_bytes.sql
- 0007_git_operations.sql
- 0008_repo_redirects.sql
- 0009_lifecycle.sql
- 0010_refs_version.sql
- 0011_artifacts_meters_forks_health.sql
- 0012_deleted_with_workspace.sql
- 0013_backups.sql
- 0014_namespace_moves.sql
- 0015_about.sql
- 0016_stats_version.sql
- 0017_push_commits.sql
- 0018_mirror.sql
- 0019_forks.sql
- 0020_push_limits.sql
- 0021_storage_copy_locks.sql
- 0022_drop_description.sql