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
- ..
- 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