Skip to content

git-cliff fails to parse context it generated itself due to missing field azure_devops #1318

@taladar

Description

@taladar

Is there an existing issue for this?

  • I have searched the existing issues

Description of the bug

I am trying to add a few variables for use in templates (in particular package.metadata.deb.revision to generate a Debian changelog) so I used the --context and --from-context options with some jq in between in my release script to add those. However, rather unexpectedly, --from-context fails due to a missing field azure_devops which I neither use in my cliff.toml, in CLI options or anywhere else.

The context.json file contains a field azureDevops in a few places so I assume there is some issue where the source code produces that but expected azure_devops when parsing.

Steps To Reproduce

  1. git cliff ... --context --output context.json
  2. git cliff ... --from-context context.json
  3. Get error like JsonError(Error("missing field azure_devops", line: 58, column: 7))

Expected behavior

I would expect it to parse the context.json it just produced itself.

Screenshots / Logs

No response

Software information

  • Operating system: Gentoo Linux
  • Rust version: 1.92.0
  • Project version: 2.11.0

Additional context

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions