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
- ..
- about.rs
- activity.rs
- addresses.rs
- alerts.rs
- archives.rs
- audit.rs
- billing.rs
- blobs.rs
- broker.rs
- caches.rs
- checks.rs
- commits.rs
- contents.rs
- coordination.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- follow.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- notifications.rs
- oauth.rs
- oidc.rs
- onboarding.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- telemetry.rs
- token_policy.rs
- toolkit.rs
- tools.rs
- why.rs