Describe the bug Fails to build.

To Reproduce

cargo +nightly  install-update koji
    Updating registry 'https://github.com/rust-lang/crates.io-index'

Package  Installed  Latest  Needs update
koji     v1.5.1     v1.5.2  Yes

Updating koji

...snip...

   Compiling cocogitto v5.2.0
   Compiling koji v1.5.2
error[E0061]: this function takes 7 arguments but 6 arguments were supplied
   --> /Users/berkus/.cargo/registry/src/github.com-1ecc6299db9ec823/koji-1.5.2/src/lib/commit.rs:43:15
    |
43  |     cocogitto.conventional_commit(&commit_type, scope, summary, body, None, is_breaking_change)?;
    |               ^^^^^^^^^^^^^^^^^^^-------------------------------------------------------------- an argument of type `bool` is missing
    |
note: associated function defined here
   --> /Users/berkus/.cargo/registry/src/github.com-1ecc6299db9ec823/cocogitto-5.2.0/src/lib.rs:364:12
    |
364 |     pub fn conventional_commit(
    |            ^^^^^^^^^^^^^^^^^^^
help: provide the argument
    |
43  |     cocogitto.conventional_commit(&commit_type, scope, summary, body, None, is_breaking_change, /* bool */)?;
    |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expected behavior Builds.

Screenshots N/A

Additional context N/A

Describe the bug The koji tool fails to run on the latest macOS. This is possibly due to dependency on OpenSSLv3.

To Reproduce Install Koji using the following command in the terminal: curl -sS https://webinstall.dev/koji | bash Run koji: koji

This problem occurs even if the release is directly downloaded from Github release page.

Expected behavior Koji should run

Screenshots dyld[54780]: Library not loaded: /usr/local/opt/openssl@3/lib/libssl.3.dylib Referenced from: ~/.local/opt/koji-v1.4.0/bin/koji Reason: tried: '/usr/local/opt/openssl@3/lib/libssl.3.dylib' (no such file), '/usr/local/lib/libssl.3.dylib' (no such file), '/usr/lib/libssl.3.dylib' (no such file) [1] 54780 abort koji

Additional context On macOS openssl version yields the following: LibreSSL 2.8.3

Describe the bug

koji --version

Error: could not find repository from '/Users/aj'; class=Repository (6); code=NotFound (-3)

Expected behavior

Should be able to print version from any directory, not just from project directories with a .git.

Describe the bug

I've got koji set up as a git hook:

.git/modules/installers/hooks/prepare-commit-msg

#!/bin/bash
koji --hook

When I run git commit -m "some description", it does not use the description that I gave:

app@beta ~/project> git commit -m "blah blah blah"
✔ What type of change are you committing? · feat
✔ What is the scope of this change? (press enter to skip) ·
? Write a short, imperative tense description of the change. ›

Expected behavior

When I run git commit -m "some description", koji should pre-populate the message with some description.

Ideally, I would like to be able to use git commit -m "feature(thing): something nice" or git commit -m "doc: more words" and koji suggest a fix for my spelling mistake, such as feat or docs.

Hey,

I had 1.2.0 installed and there was a windows version but after that version you changed the publish process and you don't built windows anymore.

Is there a limitation or something like that, why you don't provide it anymore.

Error: Not a directory (os error 20)

Describe the bug

If you're working directory is a git submodule, then .git will be a text file with the parameter gitdir acting as a (sym)link to the real module directory.

.git:

gitdir: ../.git/modules/installers

app@beta ~/project> git commit
✔ What type of change are you committing? · docs
✔ What is the scope of this change? (press enter to skip) · koji
✔ Write a short, imperative tense description of the change. · update docs for webi users as target audience
✔ Provide a longer description of the change. (press enter to skip) ·
✔ Are there any breaking changes? · No
✔ Does this change affect any open issues? · No
Error: Not a directory (os error 20)

Is your feature request related to a problem? Please describe.

First

Most config files for tooling begin with . and end in rc.<ext>:

• .jshintrc
• .eslintrc.json
• .prettierrc.json

I would prefer that koji.toml follow this convention.

Second

Most tools allow for a top-level config file in ~/.config/<name>/config.<ext>.

It would be great if koji would do this as a fallback.

For example, if I don't have a local .kojirc.toml in my git directory, but I have one in ~/.config/koji/config.toml, then that should be used instead.

Is your feature request related to a problem? Please describe.

Currently when I use koji my only option to select text is to use the arrow keys. 😢

Describe the solution you'd like

If I start typing, let's say f, then feat should be selected. Or if I type d, then docs should be selected.

config file needs to change to accept a scopes array. on first run (with --autocomplete), save the found scopes to the config via appending it. this allows the user to set up their own list when starting a fresh repo, while also populating it with new ones. every time you commit with koji, the list should be updated.

for this to work, commit_types needs to work differently. when we load a config, we need to check for commit_types and use the default if they don't exist. currently we only use the default if a config file doesn't exist at all.

this sounds like the correct thing to do, but i'm no totally sure it's necessary. autocomplete is an optional flag, and in a large repo it only slows startup down by milliseconds.