syntaqxA pushed annotated tag is announced at the commit its own tag object names (#55): with 3c9af97b live, pushing the annotated v0.0.0-tagtest2 to flagon-io/automation-lab published no git.push at all. Right after a push the store neither logs a new tag's ref nor has it in its ref advertisement yet (minutes later both have it, with its ^{} line at main), so 3c9af97b took the tag as refused; that is also why cli-v0.3.7 under 4e63b3f7 fell back to its tag object. The push itself says where the tag leads: when a push that ended within what is read moves a tag, git_http reads its pack (g1t_scan Pack) and peels each pushed tag object, following a tag of a tag, to the commit its object line names (Pushed.peeled). pushed_to announces a tag at that commit unless the advertisement has the tag elsewhere; a tag the advertisement has at the hash pushed takes its ^{} line first; one not advertised yet with nothing peeled is left to the log check, as before 3c9af97b. Deploy: repos. Checked: cargo test -p g1t-repos (370; new: a tag and a tag of a tag peeled from a real pack, lightweight tags and branches left alone; a tag not yet advertised announced at its pack's commit); cargo check -p g1t-repos --target wasm32-unknown-unknown.84f4718History
- ..
- 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