syntaqxA new repository's first push closes the issues its commits name: on flagon-io/demo the session pushed the first version with Closes #1, and #1 stayed open, so the session closed it by hand. repos' pushed lists the commits a push brought in only when the branch existed before, since a new branch's commits were pushed elsewhere first; but the push that makes the default branch is the repository's first, and nothing was pushed before it. PushedArgs has first, which work sets for a push to the default branch with no before, and their messages count then. The pull requests guide says so under Closing issues. Checked: cargo test -p g1t-repos pushed (9, one new), cargo test -p g1t-work pushed (6).9319d68History
- ..
- backup-restore-drill.mjs
- backup-restore-drill.test.mjs
- billing-live-preflight.mjs
- billing-sandbox.mjs
- detach-demo-billing.mjs
- fork-storage-test.mjs
- gitstore-namespaces.mjs
- gitstore-namespaces.test.mjs
- gitstore-usage.mjs
- platform-usage.mjs
- platform-usage.test.mjs
- restore-to-gitstore.mjs
- restore-to-gitstore.test.mjs
- runner-errors.mjs
- runner-errors.test.mjs
- smoke.mjs
- smoke.test.mjs
- sudo.mjs
- vapid-keys.mjs