fix(changelog): use root commit when --latest and there is only one tag

[kenji-miyake]

Description

Changed to use the root commit when the --latest is used and there is only one commit.

Since it uses the improved fixtures test added in #58, it depends on #58.

Motivation and Context

Generally in this case,

git commit --allow-empty -m "Initial commit"

git commit --allow-empty -m "feat: add feature 1"
git tag v0.1.0

I think people expect the following result instead of raising an error.

## [0.1.0] - 2021-01-23

### Features

- Add feature 1

How Has This Been Tested?

Please see .github/fixtures/test-latest-with-one-tag/.

Screenshots / Output (if appropriate):

Please see .github/fixtures/test-latest-with-one-tag/expected.md.

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 added tests to cover my changes.
• All new and existing tests passed.

[codecov-commenter]

Codecov Report

Merging #59 (4403240) into main (ff1d981) will decrease coverage by 0.30%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
- Coverage   40.73%   40.44%   -0.29%     
==========================================
  Files          13       13              
  Lines         825      831       +6     
  Branches      215      219       +4     
==========================================
  Hits          336      336              
- Misses        380      386       +6     
  Partials      109      109              

Impacted Files	Coverage Δ
git-cliff/src/lib.rs	0.69% <0.00%> (-0.02%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff1d981...4403240. Read the comment docs.

[orhun]

Hey, this sounds good. I'm keeping my eyes on this PR to add review when it's ready 👀

[kenji-miyake]

@orhun I'd like to let you know that I've created a setup action for git-cliff.
https://github.com/kenji-miyake/setup-git-cliff

Since you've released binaries, I was able to quickly build the action. Thank you for your work!

I think it can be another option for https://github.com/orhun/git-cliff-action.
Could you give me some comments if you have any feedback? 🙏

[orhun]

@orhun I'd like to let you know that I've created a setup action for git-cliff. kenji-miyake/setup-git-cliff

Since you've released binaries, I was able to quickly build the action. Thank you for your work!

Woo that's awesome! Thanks for doing that <3

I think it can be another option for orhun/git-cliff-action. Could you give me some comments if you have any feedback? pray

For sure! Please add it to README.md when it is ready 👍🏼

Sometimes I think I should move all git-cliff related repos to the git-cliff organization. What do you think / are you open to that?

[kenji-miyake]

@orhun Rebased and fixed some code, could you review this, please?

Woo that's awesome! Thanks for doing that <3

Thank you, I'll add it after releasing a stable tag!

Sometimes I think I should move all git-cliff related repos to the git-cliff organization. What do you think / are you open to that?

Yes, I think it's a good idea because git-cliff is a great and probably long-running product!
In that case, I will be happy to transfer my setup project there if needed.

[orhun]

Hey, sorry for the late review. This overall looks good but I have a few points that I'd like you to change. GJ 👌🏼

[kenji-miyake]

@orhun Mm... Did you have any ideas about why the test is failed?
It seems the tags() is strange if it's run without --date-order, is this related? 🤔

[orhun]

@orhun Mm... Did you have any ideas about why the test is failed? It seems the tags() is strange if it's run without --date-order, is this related?

git_log test is being run against the latest commit in the repository and it is basically checking if it is conventional or not. It was a self-perpetuating mechanism that I created for preventing unconventional commits making into the repository. And unfortunately, your last commit wasn't conventional so it fails :D

However, I pushed some conventional commits (2ad4e51 & 4403240) and now it's fixed 🎉