Artifact 1d7998b76d71136707d212b25d8832580eb6cfef5ddf1af277eb370f2d781c2c:

File examples/embed-repo-api/README.md — part of check-in [6273a0750d] at 2026-07-22 23:03:24 on branch trunk — fix: correct go.mod module path to go-libfossil (#76) (#117)
* fix: correct go.mod module path to go-libfossil (#76)
The module directive still declared github.com/danmestas/libfossil after the repository was renamed to go-libfossil. pkg.go.dev/godoc scraping matches the declared module path against its hosting path, so the stale path broke SDK doc generation.
Rename the module path across all four in-repo modules (root, the two db/driver submodules, observer/otel, and docs/site) and every internal import, plus the release workflow, the doc-generation script, and the docs.
No tag has been published under the go-libfossil path yet, so the cross-module requires cannot resolve from the proxy. Add replace directives pointing the in-repo requires at their local directories so GOWORK=off builds and the CI matrix resolve without a published version. These replaces are ignored by downstream consumers and can be dropped once new-path tags are cut.
* Guard releases against replace directives; regenerate SDK docs
The go-libfossil rename bridges the in-repo modules with `replace` directives. Go refuses a main module that carries them, so a tag cut while they are present breaks `go install .../cmd/libfossil@<tag>` and every `@version` fetch of the driver submodules. Add a Release workflow step that fails the job before anything is published if any tracked go.mod still contains a replace directive, so the bridge is a CI-enforced TODO rather than a silent landmine. The step comment records what unblocks a release: re-tag the submodules with the corrected module paths, bump the root requires, then drop the replace blocks.
Regenerate the SDK reference docs. The previous pass only substituted URLs over the pre-existing generated files, leaving stale signatures (Repo.Timeline was still documented as taking LogOpts rather than TimelineOpts). Note that gomarkdoc must be run outside a git worktree — inside one it silently strips every source link.
Also reword the README rename note, which read as though the import path had not changed, and re-sort the ncruces require block. (user: [email protected], size: 1139) [annotate] [blame] [check-ins using]

embed-repo-api

A minimal example showing how to embed libfossil as a library in a Go application. It walks the basic repo lifecycle:

Register the default pure-Go SQLite driver via blank import (_ "github.com/danmestas/go-libfossil/db/driver/modernc").
Create a new .fossil repository in a temp directory with libfossil.Create.
Close the handle returned by Create and re-open the file from disk with libfossil.Open to show the two calls are distinct.
Make one commit via repo.Commit, then read back:
- the project-code config value (repo.Config)
- the timeline of checkins (repo.Timeline)
- the files in the manifest (repo.ListFiles)
Close the repo and remove the temp directory.

Running

This example lives inside the root github.com/danmestas/go-libfossil module, so no separate go.mod is needed.

From the repo root:

go run ./examples/embed-repo-api

or:

go build ./examples/embed-repo-api

Expected output includes log lines for the created repo path, the commit RID and UUID, the project-code, one timeline entry, and one file entry (hello.txt).

Artifact [1d7998b76d]

Artifact 1d7998b76d71136707d212b25d8832580eb6cfef5ddf1af277eb370f2d781c2c:

embed-repo-api

Running