chore(release): compact the fork history at 0.9.0 #60
Labels
No labels
NaNs
area/dsh
area/forgejo
experiment
priority/later
priority/next
priority/now
type/bug
type/task
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-gitea#60
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
masteris 62+ commits ahead of the upstream base (abfd952) and almost all of them are incremental fixes. The operator's decision (2026-10-25): every minor/major release compacts the fork history a little, starting with 0.9.0. This issue is the 0.9.0 dependency that tracks it.What "compact" means
Rewrite the fork commits into a handful of logical commits before the tag, keeping the same final tree:
masteris force-pushed once, with operator approval (the single sanctioned exception to Ground rule 5);v0.8.*tags are kept, so the pre-squash commits that issues,LOGS.mdand this file quote stay resolvable;CHANGELOG.mdandLOGS.md, so nothing is lost.Mechanics (proposal)
Because the final tree is what matters, derive the compaction from the tree rather than replaying history:
Target: <= 6 fork commits on top of
abfd952, each Conventional and reviewable by path. Exact grouping is flexible; the hard requirement is the empty diff.Risks / mitigations
LOGS.md/CHANGELOG.mdstop resolving onmasterv0.8.*tags keep the objects reachable; add a one-line note toLOGS.mdthat pre-squash shas live in the tagsAcceptance
master=abfd952+ <= 6 fork commits, all Conventional and GPG-signedgit diff <old-master> masteris empty (same tree, byte for byte)npm run checkgreen on the compacted treev0.8.*tags still resolve (git tag -l,git show v0.8.8 --stat)AGENTS.md"Fork status" updated: new commit count, compaction date, and the tag ruleLOGS.mdgets a short "history compaction" section with the old->new mapping noteReferences
AGENTS.md: CI and releases → Major releases compact the history, and Ground rule 5 (the sanctioned force-push exception).v0.8.8(c47fb88) is the state to compact from.Operator decision 2026-11-08: this compaction must also purge
devops/andLOGS.mdfrom the rewritten history — both were public here and on the GitHub push mirror (devops/ since 2026-10-27). They left the tracked tree in #74 / #75 and are gitignored now, so the squash must not reintroduce them.Not force-pushing today; this issue is the sanctioned slot for the rewrite. After the squash: force-push
masteronce with operator approval, let the Forgejo push mirror follow, then verifygit log --all -- devops LOGS.mdis empty on the new refs.Follow-up to the 2026-11-08 decision: the old internal
AGENTS.md(project contract, trigger table, traps, layout, environment) was public since 0.8.2 and must be treated likedevops/— the rewrite must not reintroduce it. The publicAGENTS.mdis now a project-agnostic guide to the agents-MOC system (#76, commit29b5cfe); the project map lives in operator-localdevops/agents.md. So the 0.9.0 purge targetsdevops/,LOGS.mdand the pre-#76AGENTS.mdblobs.