chore: use stable rustfmt

[MarcoIeni]

Description

close #618

Motivation and Context

How Has This Been Tested?

Screenshots / Logs (if applicable)

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have formatted the code with rustfmt.
• I checked the lints with clippy.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 64.10256% with 28 lines in your changes missing coverage. Please review.

Project coverage is 40.15%. Comparing base (f5c39a2) to head (77b6b6b).

Files with missing lines	Patch %	Lines
git-cliff-core/src/changelog.rs	53.85%	12 Missing ⚠️
git-cliff/src/lib.rs	0.00%	8 Missing ⚠️
git-cliff-core/src/repo.rs	72.00%	7 Missing ⚠️
git-cliff-core/src/remote/mod.rs	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #834      +/-   ##
==========================================
+ Coverage   40.10%   40.15%   +0.05%     
==========================================
  Files          21       21              
  Lines        1671     1684      +13     
==========================================
+ Hits          670      676       +6     
- Misses       1001     1008       +7     

Flag	Coverage Δ
unit-tests	40.15% <64.11%> (+0.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[orhun]

We should probably cut a new point release just for these changes 💀

Do you know if there is a way of keeping the git blame while changing the formatting? I'm guessing it shouldn't be possible but it would be super nice if we can keep the historic footprint on the files somehow.

[MarcoIeni]

Yes, it's possible:

• https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
• https://www.stefanjudis.com/today-i-learned/how-to-exclude-commits-from-git-blame/

Should I add the .git-blame-ignore-revs file?

[orhun]

Wow perfect, please do it 👍🏼

[MarcoIeni]

Actually, I think we need to do this in another PR, after merging this so that we know the commit to ignore 👍

[orhun]

Can you push this again? There seems to be some conflicts.

Actually, I think we need to do this in another PR, after merging this so that we know the commit to ignore 👍

I won't do a squash merge for this PR so it should be safe to use the commit hash :)

[MarcoIeni]

I removed all unstable options. Plus edition is read from Cargo.toml

[MarcoIeni]

Ready for another look :)