syntaqxA pushed annotated tag starts its push: tags workflows, for real this time (#55): pushing cli-v0.3.7 to flagon-io/g1t, with 4e63b3f7 live, published git.push for refs/tags/cli-v0.3.7 at a41bb238, the tag object, and no CLI release started. Artifacts logs nothing for an annotated tag's ref, so pushed_to took its "cannot read back, taken as pushed" path and announced the hash the push named; Actions then read .g1t/workflows at a tag object, found none, and started nothing. 4e63b3f7's tests had a store that reads an annotated tag back as its commit, which Artifacts does not. record_push now reads the store's ref advertisement once when a push has tags (refs.rs all, as releases and refs_of do): a tag is pushed when the advertisement has it at the hash pushed, and is announced at its peeled line (refs/tags/v1^{}), the commit, or at that hash for a lightweight tag; not there or left elsewhere is refused. An advertisement that cannot be read leaves each tag to the log check as before, with an error logged. Deploy: repos. Checked: cargo test -p g1t-repos (368, new: an annotated tag the store cannot log is announced at its peeled commit; lightweight, moved elsewhere and missing tags); cargo check -p g1t-repos --target wasm32-unknown-unknown.3c9af97History
- ..
- work
- about.rs
- access.rs
- account_deletion.rs
- accounts.rs
- actions.rs
- advisories.rs
- agent_sessions.rs
- agents.rs
- ai.rs
- attachments.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