Where Does Cocogitto Store Its Config?
Cocogitto reads versioning, changelog and hook rules from cog.toml at the repo root, generatable with cog init.
Last updated
Cocogitto wants one file: cog.toml at the repository root. Commit parsers, changelog template, bump hooks and monorepo packages all live there, driving check, bump and changelog from the same source.
The tool doubles as a hook installer (cog install-hook), so the config also wires the git behavior it enforces. Keep the file strict early; loosening parsers later is easier than cleaning a history full of almost-conventional commits.
Where Cocogitto stores this, by platform
[RepoDir]\cog.toml
Parsers, changelog, pre/post bump hooks, monorepo packages. JSON schema published for editor validation. --config overrides the path per run.
[RepoDir]/cog.toml
Same file. cog commit scaffolds compliant messages interactively, which is the fastest way to learn what your own parsers demand.
[RepoDir]/cog.toml
Same layout. from_latest_tag plus tag_prefix shape which tags count; set them before the first real release or history gets sliced oddly.
Frequently asked questions
How do I create my first cog.toml?
Run cog init. It writes a template cog.toml (and an initial chore commit for new repos). Edit from there rather than composing parsers and bump profiles blank.
Can the config live outside the repo?
Pass --config <path> (default cog.toml). Remote URLs work too, which lets orgs share one versioning policy without vendoring the file.
Notice an outdated path? Let us know.