tison
Sounds reasonable. Shall we publish the image to ghcr.io? And if we'd like to support ARM architecture, perhaps we need some self-hosted runner to build.
Thanks for your updates! Let me create a tracking issue in the main repo and update the patch correspondingly.
Somehow I found this code snippet: ```rust pub trait PathBufExt { /// Append an extension to the path, even if it already has one. fn with_extra_extension(&self, extension: S) -> PathBuf;...
Updated at https://github.com/rust-lang/rust/pull/123600. PTAL.
OK. Then I can update the method name. It just to reduce the changeset in the first place.
> include a tag in the changelog even if it is skipped or in the given range I think the most understandable description is: It's hard to write reverse matches...
This is the simplified example: Before: $ GITHUB_TOKEN=*** git cliff v0.7.0..v0.7.2 # v0.7.2 Release date: April 08, 2024 ## Breaking changes * refactor!: Renames the new memtable to PartitionTreeMemtable by...
@orhun do you still need extra information?
@orhun Yeah. I can understand this alternative and it can resolve my issue. Could you write a patch in this way? I don't know how to tune the revert rules...
@orhun fixture cases pushed. You can view the expected result and do refactor as in your mind :D