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
- ..
- access.test.ts
- access.ts
- cloudflare.ts
- containers.flow.test.ts
- containers.test.ts
- containers.ts
- custom-hostnames.ts
- domains.ts
- environments.test.ts
- environments.ts
- hostname.test.ts
- hostname.ts
- index.ts
- metering.test.ts
- metering.ts
- moves.flow.test.ts
- moves.test.ts
- moves.ts
- names.test.ts
- names.ts
- redirect.test.ts
- redirect.ts
- repo-deployments.ts
- retries.test.ts
- retries.ts
- shipped.test.ts
- shipped.ts
- telemetry.test.ts
- telemetry.ts
- workflow-builds.flow.test.ts
- workflow-builds.test.ts
- workflow-builds.ts