Jérome Eertmans
Jérome Eertmans
As discussed in #2337, I think the [`git-cliff`](https://github.com/orhun/git-cliff) tool might be a good way to easily deal with CHANGELOG management. To support my point, I created this PR with some...
Hello, First, I really like your project, and I'd like to thank you for that! Second, I am quite new to this project, so I hope this question is not...
This adds a feature to generate completion files at runtime.
This skips serializing None, false, default and additional content, not needed by requests. In short, this reduces the overhead size of check requests from 291 to 29 bytes, when serialized...
This moves the "more_context"-related utilities out of the "cli" feature, because it does not realy makes sens to need "cli" to get more "context"...
This features allows to split text into fragments so that, hopefully, each fragment has a length lower than a given value. This is especially useful since the LT api limits...
Hello, Recently, I discovered that the metavar displayed in the docs is not the same as the one displayed in the command-line help output. E.g., a ```python @click.option("--config", type=click.Path(dir_okay=False)) ```...
# What I'd like to make this repo easier to manage by creating a template for feature requests. The documentation for creating templates on GitHub can be found here: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository....