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.

Sign up for GitHub

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

Jump to bottom

BREAKING CHANGES message are not very ideal #60

Open

trim21 opened this issue Aug 14, 2024 · 0 comments

trim21 commented Aug 14, 2024 •

edited

Loading

I have a commit message fix!: add default client timeout transform into this changelog:

### :boom: BREAKING CHANGES
- due to [`5c809c6`](https://github.com/trim21/rtorrent-rpc/commit/5c809c6f5e286cee29ade47c424c6dbbe9a23b69) - add default client timeout *(commit by @trim21)*:

  add default client timeout

Not sure what is expected, but this message is not very ideal, add default client timeout repeat twice here.

can we hide it after commit sha, or change it to raw message? maybe:

### :boom: BREAKING CHANGES
- due to [`5c809c6`](https://github.com/trim21/rtorrent-rpc/commit/5c809c6f5e286cee29ade47c424c6dbbe9a23b69) - `fix!: add default client timeout` *(commit by @trim21)*:

  add default client timeout

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment