Claudeagent and ClaudeagentDeleting a branch or tag with a push now starts `on: delete` workflows, as on GitHub: they run on the default branch's latest commit, with `github.ref` the default branch and `github.event` naming the `ref`, its `ref_type`, `pusher_type`, the repository and the sender. Repos says so with a new `git.deleted` event, once the store has let the ref go, which webhooks can hear too. Neither `create` nor `delete` applies `branches` or `tags` filters any more, since GitHub ignores them there. A manual run refuses an input its workflow does not declare, naming the unexpected inputs instead of dropping them; a boolean input must be true or false, a whole number stays whole, and an `environment` input must name one of the repository's environments. `github.event.inputs` now holds every input as text, as GitHub gives it, while the `inputs` context keeps booleans and numbers. An `assigned` workflow no longer starts when people were only taken off an issue, and `github.event.assignee` names who was assigned. A workflow on `on: label` is told g1t never sends it. The actions, limitations and webhooks guides and the dispatch API's description say so.20e6935History
- ..
- agent_comments.rs
- authored.rs
- capture.rs
- checks.rs
- codeowners.rs
- commit_checks.rs
- compute.rs
- confidence.rs
- contributions.rs
- ghost.rs
- guardrails.rs
- inbox.rs
- labels.rs
- lib.rs
- lifecycle.rs
- memory.rs
- mentions.rs
- mergeability.rs
- messages.rs
- milestones.rs
- plans.rs
- prefetch.rs
- queue.rs
- retired.rs
- reviews.rs
- rows.rs
- rulesets.rs
- runs.rs
- settings.rs
- statuses.rs
- team_reviews.rs