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
- ..
- 0001_init.sql
- 0002_dependencies.sql
- 0003_repo_deleted.sql
- 0004_repo_archived.sql
- 0005_description_inherits.sql
- 0006_workspace_deleted.sql
- 0007_deploys.sql
- 0008_pins.sql
- 0009_activity.sql
- 0010_kind_and_links.sql
- 0011_drop_dependencies.sql
- 0012_production_image.sql
- 0013_reports_production.sql
- 0014_descriptions_are_projects.sql
- 0015_drop_repo_description.sql
- 0016_sweeps.sql