Skip to content

History and versions

Git holds one commit per published task, SpecsGraph records a spec version per landing, and a workstream shows what it changes against Main.

Git is the history of Main

Every landing is a commit of the YAML files in your spec folder, either a direct commit or the merged pull request. The commit names the task in its message and carries trailers:

  • Spec-Task, Spec-Workstream and Spec-Published-By;
  • Co-authored-by for each author;
  • Refs for the tracker key, and Decision lines for the decisions it records.

git log and git blame on the spec folder answer who changed what, when and why:

TerminalShell
# Every landing on this branch, newest first
git log --oneline -- specsgraph/

# Landings of one story
git log --oneline --grep "KAN-43" -- specsgraph/

Spec versions

Each landing records a spec version, a sequence number per project, with the task and the publication, and the revision of every artefact it changed. A publish that changes nothing records none.

Files edited in the repository outside SpecsGraph are detected at landing, and the next publish of such a file is blocked until an Admin overwrites it.

Inside a workstream

The Changes page is the history of a workstream against Main: what changed, the diff and who changed it last. Discarding a change and resolving a conflict are recorded as revisions of the artefact too.

What is not there yet

A list of spec versions in the app, and reverting a published task, are not available yet. Until then, revert by editing the artefacts back in a new workstream and publishing that task.

Next steps