Skip to content

docs: Add git-cliff configuration, update changelog#1129

Merged
Czaki merged 2 commits into
developfrom
cliff_config
Jul 8, 2024
Merged

docs: Add git-cliff configuration, update changelog#1129
Czaki merged 2 commits into
developfrom
cliff_config

Conversation

@Czaki

@Czaki Czaki commented Jul 8, 2024

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Chores
    • Introduced configuration options for git-cliff to streamline and automate the generation of changelogs.

@Czaki Czaki added this to the 0.15.3 milestone Jul 8, 2024
@coderabbitai

coderabbitai Bot commented Jul 8, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The cliff.toml file has been enriched with configurations for git-cliff, a tool used to generate changelogs. It establishes templates for different sections of the changelog, includes postprocessors for handling URLs, and sets rules for parsing commit messages in accordance with the conventional commits specification.

Changes

File Change Summary
cliff.toml Introduced templates for changelog header, body, and footer; added URL postprocessors; defined commit parsing rules.

Poem

In the heart of software's lore,
A changelog tailored, crafted more.
Templates set and rules align,
Commits now in perfect sign.
Hail to `cliff.toml`, our guiding star,
In changelog's realm, it shines afar.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sourcery-ai

sourcery-ai Bot commented Jul 8, 2024

Copy link
Copy Markdown
Contributor

🧙 Sourcery has finished reviewing your pull request!


Tips
  • Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
  • Continue your discussion with Sourcery by replying directly to review comments.
  • You can change your review settings at any time by accessing your dashboard:
    • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
    • Change the review language;
  • You can always contact us if you have any questions or feedback.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

@sonarqubecloud

sonarqubecloud Bot commented Jul 8, 2024

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Outside diff range and nitpick comments (10)
changelog.md (10)

98-98: Typographical error: Use "properly" instead of "proper".

The word “proper” is an adjective and doesn’t fit in this context. Did you mean the adverb “properly”?

- Fix `make_release.yml` to proper detect release, attempt 3
+ Fix `make_release.yml` to properly detect release, attempt 3
Tools
LanguageTool

[misspelling] ~98-~98: The word “proper” is an adjective and doesn’t fit in this context. Did you mean the adverb “properly”?
Context: ...pull/1126)) - Fix make_release.yml to proper detect release, attempt 3 ([#1127](http...

(ADJECTIVE_ADVERB)


88-88: Typographical error: Use "macOS" instead of "macos".

The operating system from Apple is written “macOS”.

- Bump macos runners to macos-13 (both azure and GHA)
+ Bump macOS runners to macOS-13 (both azure and GHA)
Tools
LanguageTool

[grammar] ~88-~88: The operating system from Apple is written “macOS”.
Context: ...m//pull/1103)) - Bump macos runners to macos-13 (both azure and GHA...

(MAC_OS)


125-125: Grammar correction: Use "selecting" instead of "select".

Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

- Do not allow to select and render corrupted batch plans
+ Do not allow selecting and rendering corrupted batch plans
Tools
LanguageTool

[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)


154-154: Grammar correction: Add a comma before ‘but’.

Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).

- read tiff files with double `Q` in axes but one related to dummy dimension
+ read tiff files with double `Q` in axes, but one related to dummy dimension
Tools
LanguageTool

[uncategorized] ~154-~154: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... read tiff files with double Q in axes but one related to dummy dimension ([#992](...

(COMMA_COMPOUND_SENTENCE_2)


155-155: Typographical error: Capitalize "Excel".

Capitalize this word if you mean the computer program “Excel”.

- when saving calculation plan to excel file
+ when saving calculation plan to Excel file
Tools
LanguageTool

[grammar] ~155-~155: Capitalize this word if you mean the computer program “Excel”.
Context: ...d state when saving calculation plan to excel file ([#995](https://github.com/4DNucle...

(ON_EXCEL)


183-183: Grammar correction: Use "seeing" instead of "see".

Did you mean “seeing”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

- Allow to see underlying exception when show warning caused by exception
+ Allow seeing underlying exception when show warning caused by exception
Tools
LanguageTool

[grammar] ~183-~183: Did you mean “seeing”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...m//pull/802)) - Allow to see underlying exception when show warning ...

(ALLOW_TO)


323-323: Grammar correction: Use "customize" instead of "customize".

The preposition ‘to’ may be missing (allow someone to do something).

- Allow customize settings directory using the `PARTSEG_SETTINGS_DIR` environment variable
+ Allow to customize settings directory using the `PARTSEG_SETTINGS_DIR` environment variable
Tools
LanguageTool

[grammar] ~323-~323: The preposition ‘to’ may be missing (allow someone to do something).
Context: ...m//pull/733)) - Allow customize settings directory using the `PARTSEG_S...

(ALLOW_TO_DO)


335-335: Grammar correction: Use "do not create" instead of "to do not create".

Are you sure the preposition ‘to’ or the verb ‘do’ is correct here?

- Fix bug in cut with roi to do not make black artifacts
+ Fix bug in cut with roi to not make black artifacts
Tools
LanguageTool

[grammar] ~335-~335: Are you sure the preposition ‘to’ or the verb ‘do’ is correct here?
Context: ...eg/pull/765)) - Fix bug in cut with roi to do not make black artifacts ([#767](https://gi...

(NEGATED_INFINITIVE)


434-434: Grammar correction: Use "creation" instead of "create".

The word ‘create’ is a verb. Did you mean the noun “creation”?

- Refactor the create batch plan widgets and add test for it
+ Refactor the creation of batch plan widgets and add test for it
Tools
LanguageTool

[grammar] ~434-~434: The word ‘create’ is a verb. Did you mean the noun “creation”?
Context: .../598)) ### 🚜 Refactor - Refactor the create batch plan widgets and add test for it ...

(PREPOSITION_VERB)


453-453: Typographical error: Capitalize "Excel".

Capitalize this word if you mean the computer program “Excel”.

- import calculation plan from batch result excel file
+ import calculation plan from batch result Excel file
Tools
LanguageTool

[grammar] ~453-~453: Capitalize this word if you mean the computer program “Excel”.
Context: ...port calculation plan from batch result excel file ([#567](https://github.com/4DNucle...

(ON_EXCEL)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8c1e07b and e5b29c1.

Files selected for processing (2)
  • changelog.md (1 hunks)
  • cliff.toml (1 hunks)
Files not summarized due to errors (1)
  • changelog.md: Error: Message exceeds token limit
Additional context used
LanguageTool
changelog.md

[grammar] ~88-~88: The operating system from Apple is written “macOS”.
Context: ...m//pull/1103)) - Bump macos runners to macos-13 (both azure and GHA...

(MAC_OS)


[misspelling] ~98-~98: The word “proper” is an adjective and doesn’t fit in this context. Did you mean the adverb “properly”?
Context: ...pull/1126)) - Fix make_release.yml to proper detect release, attempt 3 ([#1127](http...

(ADJECTIVE_ADVERB)


[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)


[uncategorized] ~154-~154: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... read tiff files with double Q in axes but one related to dummy dimension ([#992](...

(COMMA_COMPOUND_SENTENCE_2)


[grammar] ~155-~155: Capitalize this word if you mean the computer program “Excel”.
Context: ...d state when saving calculation plan to excel file ([#995](https://github.com/4DNucle...

(ON_EXCEL)


[grammar] ~183-~183: Did you mean “seeing”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...m//pull/802)) - Allow to see underlying exception when show warning ...

(ALLOW_TO)


[grammar] ~323-~323: The preposition ‘to’ may be missing (allow someone to do something).
Context: ...m//pull/733)) - Allow customize settings directory using the `PARTSEG_S...

(ALLOW_TO_DO)


[grammar] ~335-~335: Are you sure the preposition ‘to’ or the verb ‘do’ is correct here?
Context: ...eg/pull/765)) - Fix bug in cut with roi to do not make black artifacts ([#767](https://gi...

(NEGATED_INFINITIVE)


[grammar] ~434-~434: The word ‘create’ is a verb. Did you mean the noun “creation”?
Context: .../598)) ### 🚜 Refactor - Refactor the create batch plan widgets and add test for it ...

(PREPOSITION_VERB)


[grammar] ~453-~453: Capitalize this word if you mean the computer program “Excel”.
Context: ...port calculation plan from batch result excel file ([#567](https://github.com/4DNucle...

(ON_EXCEL)

Additional comments not posted (15)
cliff.toml (10)

10-13: Header template looks good!

The header template is correctly defined.


16-30: Body template looks good!

The body template is correctly defined and uses Tera template syntax.


32-34: Footer template looks good!

The footer template is correctly defined.


38-40: Postprocessors configuration looks good!

The postprocessor for replacing the repository URL is correctly defined.


44-46: Commit parsing options look good!

The options for parsing conventional commits and filtering unconventional commits are correctly defined.


50-56: Commit preprocessors configuration looks good!

The commit preprocessors for handling issue numbers and spelling checks are correctly defined.


60-74: Commit parsers configuration looks good!

The regex patterns for parsing and grouping commits are correctly defined.


92-93: Bump strategy configuration looks good!

The option for determining the version bump strategy is correctly defined.


79-84: Tag patterns configuration looks good!

The regex patterns for matching and skipping git tags are correctly defined.


87-88: Sort commits configuration looks good!

The option for sorting commits inside sections by oldest order is correctly defined.

changelog.md (5)

125-125: Grammar correction: Use "selecting" instead of "select".

Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

Tools
LanguageTool

[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)


125-125: Grammar correction: Use "selecting" instead of "select".

Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

Tools
LanguageTool

[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)


453-453: Typographical error: Capitalize "Excel".

Capitalize this word if you mean the computer program “Excel”.

Tools
LanguageTool

[grammar] ~453-~453: Capitalize this word if you mean the computer program “Excel”.
Context: ...port calculation plan from batch result excel file ([#567](https://github.com/4DNucle...

(ON_EXCEL)


125-125: Grammar correction: Use "selecting" instead of "select".

Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

Tools
LanguageTool

[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)


125-125: Grammar correction: Use "selecting" instead of "select".

Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.

Tools
LanguageTool

[grammar] ~125-~125: Did you mean “selecting”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...eome/PartSeg/pull/1016)) - Do not allow to select and render corrupted batch plans ([#101...

(ALLOW_TO)

@codecov

codecov Bot commented Jul 8, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.94%. Comparing base (8c1e07b) to head (e5b29c1).
Report is 73 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1129      +/-   ##
===========================================
+ Coverage    92.93%   92.94%   +0.01%     
===========================================
  Files          205      205              
  Lines        32519    32519              
===========================================
+ Hits         30220    30225       +5     
+ Misses        2299     2294       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Czaki Czaki changed the title Add git-cliff configuration, update changelog doc: Add git-cliff configuration, update changelog Jul 8, 2024
@Czaki Czaki changed the title doc: Add git-cliff configuration, update changelog docs: Add git-cliff configuration, update changelog Jul 8, 2024
@Czaki Czaki merged commit 113dc1b into develop Jul 8, 2024
@Czaki Czaki deleted the cliff_config branch July 8, 2024 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant