publisher/

directory
v0.28.2 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 5, 2026 License: Apache-2.0

Directories

Path Synopsis
Package checkcmd is `ovdb publisher check`: it checks the Git repository in a directory, as committed at HEAD, with the Publisher profile of package repo, and prints what it finds for a person or, with --json, as a document for a CI job.
Package checkcmd is `ovdb publisher check`: it checks the Git repository in a directory, as committed at HEAD, with the Publisher profile of package repo, and prints what it finds for a person or, with --json, as a document for a CI job.
Package exitcode is the error type that the publisher commands return for a failure that is not a finding: bad usage, or an environment that cannot run the command.
Package exitcode is the error type that the publisher commands return for a failure that is not a finding: bad usage, or an environment that cannot run the command.
Package manifest judges a publisher's OVDB.md and OVDB manifest (ovdb.yaml) as pure functions over the bytes of the two documents: no file system, no git, no network.
Package manifest judges a publisher's OVDB.md and OVDB manifest (ovdb.yaml) as pure functions over the bytes of the two documents: no file system, no git, no network.
Package repo judges a whole repository against the Chinook checker: OVDB.md and the manifests it lists, and the files an own-form manifest names, are tracked regular files of the commit at HEAD, as committed and never from the working tree; every manifest is judged with package manifest; publisher.repository is the --repository given; and what the model file and the meaning file say agrees with the manifest (the module, the entities and the recordsets, the id, the license and the models: entry).
Package repo judges a whole repository against the Chinook checker: OVDB.md and the manifests it lists, and the files an own-form manifest names, are tracked regular files of the commit at HEAD, as committed and never from the working tree; every manifest is judged with package manifest; publisher.repository is the --repository given; and what the model file and the meaning file say agrees with the manifest (the module, the entities and the recordsets, the id, the license and the models: entry).
Package rules holds the pure rules that a publisher's OVDB manifest is held to: what a published URL, a homepage, a database id, a commit, a repository, a path inside a repository, an engine name and a licence id may look like, and how two claimed addresses compare.
Package rules holds the pure rules that a publisher's OVDB manifest is held to: what a published URL, a homepage, a database id, a commit, a repository, a path inside a repository, an engine name and a licence id may look like, and how two claimed addresses compare.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL