@uscreen.de/dev-repo
Advanced tools
Manage a group of repositories for local development
Add the module within your dev repo:
$ yarn add @uscreen.de/dev-repo
To combine mutliple repositories into one single development repository you just add a mapping to your existing package.json, ie.:
"repos": {
"client": "git@github.com:example/client.git",
"api": "git@github.com:example/api.git",
"website": "git@github.com:example/website.git"
}
Next run repo install and you will end up with a directory structure like:
.
├── package.json
├── repos
│ ├── client
│ ├── api
│ └── site
└── yarn.lock
Each ./repos/* now containing a git cloned checkout with ./repos/*/node_modules already installed. Invoking $ repowithout any parameter prints general usage information:
$ repo
Usage: repo [options] [command]
Options:
-V, --version output the version number
-h, --help output usage information
Commands:
install [repository] install named repository (ie. "webapi"), or all if no name supplied
list [repository] [-f|--fetch] list named repository (ie. "webapi"), or all if no name supplied
pull [repository] pull named repository (ie. "webapi"), or all if no name supplied
run <command> [repository] run command within named repository (ie. "webapi"), or all if no name supplied
help [cmd] display help for [cmd]
Install given repository or all. This will create any missing subdirectory, git clone missing repositories and run a yarn install for each repository. Subsequent calls of repo install will at least run a yarn install each time. Those will run in parallel.
Pull one given repository from remote or all repositories. Those pulls will run in parallel.
Run given command within given repository or all available repositories. Example with three repoos:
$ repo run "git pull"
Already up to date.
Already up to date.
Already up to date.
Example with a given repository:
$ repo run "git status" webapi
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
By now commands will run in parallel, so don't expect a proper sequences output. run inherits the current users shell from env to enable aliases etc. by default. For example this could open editors for all projects:
$ repo run "v"
(assuming an alias like alias v 'code .')
Lists local information about a given repository or all.
Example output:
$ repo list
client@0.1.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD dirty [2⇡/⇣1] - Working Copy: 2 uncommitted local changes
website@0.3.0 - [stable] HEAD clean
$ repo list
client@0.1.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD dirty [2⇡/⇣1]
website@0.3.0 - [stable] HEAD clean
$ repo list
client@0.1.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD dirty [3⇡/⇣0]
website@0.3.0 - [stable] HEAD clean
$ repo list
client@0.1.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD clean - Working Copy: 1 uncommitted local changes
website@0.3.0 - [stable] HEAD clean
$ repo list
client@0.1.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD clean - Working Copy: 1 uncommitted local changes
website@0.3.0 - [stable] HEAD clean
$ repo list -f
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 2 (delta 1), reused 1 (delta 1)
Unpacking objects: 100% (2/2), done.
From github.com:example/api
b578056..d7b07cd master -> origin/master
website@0.3.0 - [master] HEAD clean
api@0.4.0 - [master] HEAD dirty [0⇡/⇣1]
client@0.1.0 - [master] HEAD clean
repo pull command to pull one or all repositories from remoterepo run command to run sub-commands within repositoriesrepo install command to install from git & npmrepo list command to give some status inforepo list --fetch to also git fetch befores listLicensed under MIT.
Published, Supported and Sponsored by u|screen
FAQs
cli to manage dev repos
We found that @uscreen.de/dev-repo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.