Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions git-cliff-core/src/commit.rs
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,8 @@ impl Serialize for Commit<'_> {
commit.serialize_field("gitea", &self.gitea)?;
#[cfg(feature = "bitbucket")]
commit.serialize_field("bitbucket", &self.bitbucket)?;
#[cfg(feature = "azure_devops")]
commit.serialize_field("azure_devops", &self.azure_devops)?;
Copy link
Contributor

@ognis1205 ognis1205 Dec 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using Camel Case in JSON is the established convention. Can we change this to azureDevops instead?

This looks good to me.

if let Some(remote) = &self.remote {
commit.serialize_field("remote", remote)?;
}
Expand Down
1 change: 1 addition & 0 deletions git-cliff-core/src/release.rs
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ pub struct Release<'a> {
pub bitbucket: RemoteReleaseMetadata,
/// Contributors.
#[cfg(feature = "azure_devops")]
#[serde(rename = "azure_devops")]
Copy link
Contributor

@ognis1205 ognis1205 Dec 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need this change?

This looks good to me.

pub azure_devops: RemoteReleaseMetadata,
}

Expand Down
Loading