feat: add --allow-no-commit to changelog command

[bearomorphism]

… but changelog command raised NoCommitsFoundError

Fixes #1866

Description

Checklist

• I have read the contributing guidelines

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Code Changes

• Add test cases to all the changes you introduce
• Run uv run poe all locally to ensure this change passes linter check and tests
• Manually test the changes:
  • Verify the feature/bug fix works as expected in real-world scenarios
  • Test edge cases and error conditions
  • Ensure backward compatibility is maintained
  • Document any manual testing steps performed
• Update the documentation for the changes

Documentation Changes

• Run uv run poe doc locally to ensure the documentation pages renders correctly
• Check and fix any broken links (internal or external)

Expected Behavior

Steps to Test This Pull Request

Additional Context

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.99%. Comparing base (dd972c9) to head (72403ad).
⚠️ Report is 62 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1868   +/-   ##
=======================================
  Coverage   97.98%   97.99%           
=======================================
  Files          60       60           
  Lines        2686     2693    +7     
=======================================
+ Hits         2632     2639    +7     
  Misses         54       54           

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

[Copilot]

Pull request overview

Fixes cz bump --allow-no-commit failures when update_changelog_on_bump = true and there are no commits between bumps (Issue #1866), by ensuring changelog generation doesn’t raise NoCommitsFoundError in that scenario.

Changes:

• Adds an allow_no_commit flag to the internal Changelog command arguments and uses it to skip the “No commits found” error.
• Passes allow_no_commit from the bump command into the changelog command invocation.
• Adds a regression test covering bumping prereleases with --allow-no-commit while updating the changelog.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
commitizen/commands/changelog.py	Accepts/stores allow_no_commit and uses it to suppress NoCommitsFoundError when there are no commits.
commitizen/commands/bump.py	Forwards allow_no_commit into changelog generation during bump.
tests/commands/test_bump_command.py	Adds a regression test reproducing Issue #1866.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[woile]

Please also update the documentation explaining the behavior of changelog when allow_no_commit is True and what it does 🙏🏻

Like what is mention in the OP ticket #1866 could be a good idea:

alter the CHANGELOG to indicate there has been a release but nothing has changed

[bearomorphism]

[AI-generated comment]\n\nAddressed the latest review feedback in 7d59bf4:\n- clarified internal typing/intent for allow_no_commit in changelog\n- normalized forwarded allow_no_commit to bool in bump\n- simplified the regression test setup\n- added docs for changelog behavior when --allow-no-commit is used with bump-triggered changelog generation\n\nValidated with:\nuv run pytest tests/commands/test_bump_command.py -k "allow_no_commit_issue or allow_no_commit_with_no_commit" -q\n(2 passed)

[bearomorphism]

Let me draft this PR... I think I need to fix it manually

[woile]

I agree, I think we should allow the new flag in cz changelog. This would mean it's a new feature.

[Lee-W]

overall looks good, also looks like a feature to me