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
- ..
- work
- about.rs
- access.rs
- account_deletion.rs
- accounts.rs
- actions.rs
- advisories.rs
- agent_sessions.rs
- agents.rs
- ai.rs
- audit.rs
- backups.rs
- billing.rs
- checks.rs
- codeowners.rs
- coding_agents.rs
- credentials.rs
- datasets.rs
- decisions.rs
- deploy_keys.rs
- events.rs
- folios.rs
- github.rs
- guardrails.rs
- identity.rs
- ids.rs
- inbox.rs
- integrations.rs
- lib.rs
- live.rs
- members.rs
- names.rs
- outcome.rs
- packages.rs
- people.rs
- projects.rs
- repos.rs
- rules.rs
- runners.rs
- scopes.rs
- search.rs
- security.rs
- security_suite.rs
- subscribers.rs
- teams.rs
- time.rs
- tokens.rs
- updates.rs
- webhooks.rs
- work.rs