mo

Manage your Opensource projects!

mo keeps your GitHub repos organized under a single root directory.

Install

npm i -g @liangmi/mo

Requirement

• macOS or Linux
• git
• GitHub CLI gh authenticated (gh auth status)

Setup

Run once to initialize config and shell integration:

mo setup

Commands

| Command | Alias | Description | | ----------------- | ------- | ------------------------------------------- | | mo setup | | Initialize config and shell integration | | mo clone <repo> | mo c | Clone <owner>/<repo> or a GitHub repo URL | | mo fork [repo] | mo f | Fork <owner>/<repo>, a GitHub URL, or cwd | | mo list | mo ls | List all managed repos | | mo cd [query] | | Jump to root, owner, or repo directory | | mo edit [query] | mo e | Open a directory in your editor | | mo open [query] | mo o | Open a directory in Finder/Explorer |

mo cd, mo edit, and mo open has the similar behavior and they open an interactive selector when called without arguments.

[!TIP] If you are using mo with VS Code based editors, you can add this line to your editor config to prevent mo edit popping up a new separated window.

"window.openFoldersInNewWindow": "off"

Setting code -r as your editor in mo setup have the same effect as well.

Config

The config file should be generated by running mo setup. Modifying ~/.config/morc.json manually is not recommended.

Please follow the config_schema.json if you are developing mo.

~/.config/morc.json:

{
  "$schema": "https://raw.githubusercontent.com/liangmiQwQ/mo/main/config_schema.json",
  "root": "~/code",
  "shells": ["zsh"],
  "editor": "code",
  "alias": {
    "clone": ["k"],
    "cd": ["i"],
    "edit": ["e"]
  }
}

Contribution

We are so excited that you are willing to help improving mo! Please see ROADMAP.md for what's planned.

License

MIT © Liang Mi