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
- ..
- coordination
- attachments.rs
- authored.rs
- automerge.rs
- checks.rs
- closing.rs
- codeowners.rs
- commit_checks.rs
- commit_comments.rs
- contributions.rs
- decisions.rs
- ghost.rs
- guardrails.rs
- head_repo.rs
- inbox.rs
- insights.rs
- insights.sql
- integration.rs
- labels.rs
- lib.rs
- lifecycle.rs
- merge_message.rs
- mergeability.rs
- merging.rs
- milestones.rs
- prefetch.rs
- pushed.rs
- queue.rs
- queue_tests.rs
- reactions.rs
- retired.rs
- reviews.rs
- rows.rs
- rulesets.rs
- runs.rs
- settings.rs
- statuses.rs
- team_reviews.rs