When running yggit (on my dev branch) I get the following error after correctly entering my pin and touching my Yubikey:

cargo run -- push           
   Compiling yggit v0.0.1 (/home/d4hines/repos/yggit)
    Finished dev [unoptimized + debuginfo] target(s) in 0.73s
     Running `target/debug/yggit push`
Setting branch d4hines/more-characters to commit 3c12c3313056fd57fde672ae1076d8adc2b59815
Setting branch d4hines/nix to commit 0fc6732a9cce20673d2d64b00a5497ff86caee09
thread 'main' panicked at src/git/git.rs:143:14:
fetch repository has fialed: Error { code: -1, klass: 0, message: "all authentication attempts failed" }
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: core::result::Result<T,E>::expect
             at /build/rustc-1.75.0-src/library/core/src/result.rs:1034:23
   4: yggit::git::git::Git::find_remote_head
             at ./src/git/git.rs:136:9
   5: yggit::core::push_from_notes
             at ./src/core.rs:88:29
   6: yggit::commands::push::Push::execute
             at ./src/commands/push.rs:42:9
   7: yggit::main
             at ./src/main.rs:34:33
   8: core::ops::function::FnOnce::call_once
             at /build/rustc-1.75.0-src/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

The ssh-agent is definitely prompting the Yubikey, but it looks like Yggit is somehow not properly looking for the response.

I am always working on one branch because it's the purpose of this tool.

But the command yggit push is not pushing the current branch (with lease)

Better error

I am using unit as error in too many space. Or I am using string. It's not the way to do it.

It would be nice to return meaningful error. By using anyhow and/or thiserror

The title is just some sarcasm, 'cause I love that

When working on gitlab, when a fixup commit is pushed, the MR is set to draft... Even if it's ready
I propose to add some symbols:

-> <branch> # Would mean push on "branch" and set the associated MR to ready

?? <branch> # Would mean push on "branch" and set the associated MR to draft

Still don't know if the status of the MR has to be retrieved from gitlab or not

I should explain my git workflow in details on the readme

So that I can convince the world to use this tool

Git might be awesome, but it seems that the .gitconfig format is not yaml 🤔
Or at least I cannot parse it with the library I used in the project.

The goal is to remove this library and avoid asking the user to adapt its configuration, for instance strings has to be between quotes, but git does not add these quotes for string in the configuration

I don't know why, but I didn't succeed to use the ssh-agent of my machine to get my private key and sign payload
That's why the path is defined in the .gitconfig

There should be a way

I love to use git rebase -i master --exec "run-test"
But, sometimes, the command differ from a commit to another one
Maybe we can add a command:

yggit test

That instead of setting a branch to a commit, it will write the test command in the commit note and execute the test rebase.
Then it's super convenient to test commits:

• because you don't have to remember your test command
• because you can have a test command unique per commit

The last point is important, for instance when working on a bug, I like to write a test commit, and then to write the fix. The test commit does not pass the tests, and the fix fixes it.

We can imagine the following interface:

<commit-hash> <commit-name>
<exec|e> command

Like rebase x)
Of course the branch should not be printed

Versioning

Well, I don't understand how crates.io works, but I think it's imperative that the version in the Cargo.toml is the same as the latest tag.

I propose to push the commit from the publish action