Skip to content

fix(util): fixes no-op log output when commit message contains square-brackets #1287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

codejedi365
Copy link
Contributor

@codejedi365 codejedi365 commented Jun 30, 2025

Purpose

Rationale

How did you test?

How to Verify


PR Completion Checklist

  • Reviewed & followed the Contributor Guidelines

  • Changes Implemented & Validation pipeline succeeds

  • Commits follow the Conventional Commits standard
    and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)

  • Appropriate Unit tests added/updated

  • Appropriate End-to-End tests added/updated

  • Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)

@codejedi365 codejedi365 changed the title fix(util): fixes no-op log output when commit message contains square… fix(util): fixes no-op log output when commit message contains square-brackets Jun 30, 2025
@codejedi365 codejedi365 merged commit f25883f into python-semantic-release:master Jul 1, 2025
13 checks passed
@codejedi365 codejedi365 deleted the fix/rich-log-output branch July 1, 2025 00:46
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.

bug: No-op mode fails to log any bracket-encased text in commit_message
1 participant