Thanks for a nice tool!

I have a trouble that ghr list command does not work. I'd love to know if you have any solution.

❯ ghr list
error: The subcommand 'list' wasn't recognized

Usage: ghr <COMMAND>

For more information try '--help'

Other commands, such as ghr cd, ghr clone or ghr delete is working as expected.

My environment

OS: macOS Monterey shell: fish version:

❯ ghr version
ghr v0.2.2 built with rustc 1.65.0 (897e37553 2022-11-02) at 2022-11-29 03:20:54Z

Hi, @siketyan. I have been using your ghr. Source code management has become very comfortable. Thank you very much!!!

This PR fixes a small bug that caused the interactive shell to exit when executing commands that fail after installing the bash extension.

$ echo 'eval "$(ghr shell bash)"' >> .bashrc # or other shell config file

$ exec $SHELL -l

$ false # interactive shell exit here

This problem was caused by set -e in resources/shell/ghr.bash, so this line has been removed. Similarly, set -u has been removed because it may cause problems for some users (as it did for me).

Thank you!

Bumps tokio from 1.21.2 to 1.23.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

ghr now supports resolving only pattern if you have setup the default owner. Setting the default is so easy:

[defaults]
owner = "siketyan"

Add this to your ghr.toml and done!

Now you can init/clone/open/delete repos without specifying the owner.

ghr clone <repo>

Before implementing #7, we need to know what repositories are managed under the ghr root. We need to walk directories in the root and find all directories matching <host>/<owner>/<repo>.

Closes #14

Now you can open in some of application such as code, phpstorm, clion and more without any configuration, if the app supports opening by invoking in [cmd] [path] format.

Closes #2

After cloned a repository, we often want to open some application such as IDE or editor in the cloned repository directory. We utilised that in a simple way.

To use this feature, you need to configure applications you want to open first. The following example shows an application entry opening Visual Studio Code.

[applications.vscode]
cmd = "code"
args = ["%p"]

Note that an argument %p is replaced by the actual repository path.

Now you can use ghr clone --open or ghr open:

ghr clone siketyan/ghr --open vscode
ghr open siketyan/ghr vscode

The Git backend ghr uses was libgit2 in v0.1 releases. However, in this strategy, we could not clone repository in an authenticated context (e.g. cloning your private repo, or your organisation's repo).

Now ghr uses Git CLI (git command simply) by default. You can also change this behaviour by modifying config.toml file as follows:

[git]
stategy.clone = "git2"  # `cli` or `git2`

Have fun!

ghr open, ghr init --open, and ghr clone --open requires specifying what application to open currently. When opening the repo in the associated application (i.e. Finder on macOS), we need to specify them as ghr open <repo> open or ghr clone <repo> --open open. It's a little complicated and not easy to understand.

So we need to open repository in the associated app by default, without specifying what app to open. i.e. ghr open <repo> opens the repo in the app.

ghr clone siketyan/test --init npm

will run npm i in the repository directory after cloning. It requires configuration before using the feature.

[initializers.npm]
cd = { cmd = "npm", args = ["i"] }
default = { cmd = "npm", args = ["ci"] }

With the configuration above, ghr will execute npm i after ghr cd, otherwise npm ci.