Thanks!
> Did you consider the recent git nomenclature change to use "switch" for branch operations, and "co" for file operations?
Actually, isn't "restore" for file operations? My impression was that everyone agrees that `git checkout` does too many different things. In particular, it's both for switching branches and for restoring file content. So they added the new `git switch` and `git restore` with limited scope. I strongly suspect that they would have used `git checkout` for the former if that wasn't already taken by the existing command.
> And, do you have plans on supporting signed commits, either via gpg or the newfound SSH key signing?
No, that's not something I've even started thinking about. I'll have to read up on how it works in Git first. Patches welcome, though :)
> I'm super excited to try out the conflict resolution mechanism, because that's a major painpoint for my long-lived PR branches
You mean so you can continuously rebase them without having to resolve conflicts right away? Yes, that's one of the benefits of first-class conflicts. Another benefit, which took me a long time to realize how useful it is, is the auto-rebase feature.
> Did you consider the recent git nomenclature change to use "switch" for branch operations, and "co" for file operations?
Actually, isn't "restore" for file operations? My impression was that everyone agrees that `git checkout` does too many different things. In particular, it's both for switching branches and for restoring file content. So they added the new `git switch` and `git restore` with limited scope. I strongly suspect that they would have used `git checkout` for the former if that wasn't already taken by the existing command.
> And, do you have plans on supporting signed commits, either via gpg or the newfound SSH key signing?
No, that's not something I've even started thinking about. I'll have to read up on how it works in Git first. Patches welcome, though :)
> I'm super excited to try out the conflict resolution mechanism, because that's a major painpoint for my long-lived PR branches
You mean so you can continuously rebase them without having to resolve conflicts right away? Yes, that's one of the benefits of first-class conflicts. Another benefit, which took me a long time to realize how useful it is, is the auto-rebase feature.