alibaba / git-repo-go

git-repo is a command-line tool for centralized workflow, can work with Gerrit, AGit-Flow compatible servers. It is written in Golang, and it can be installed easily without further dependency. It provides an easy-to-use solution for multiple repositories which is introduced by Android repo first, and it can also work with a single repository.

Home Page:https://git-repo.info/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not all commands from `repo` implemented in `git-repo-go`

obalunenko opened this issue · comments

git-repo-go could not be used as a drop-in replacement as not all commands from repo implemented yet.

Version: v0.7.8

Help of git-repo-go

Usage:
  git-repo [flags]
  git-repo [command]

Available Commands:
  abandon     Permanently abandon a development branch with --force option
  download    Download and checkout a code review
  filter      Content filter drivers for git
  forall      Run a shell command in each project
  help        Help about any command
  init        Initialize manifest repo in the current directory
  list        List projects and their associated directories
  manifest    Manifest inspection utility
  prune       Prune (delete) already merged topic branches
  start       Start a new branch for development
  status      Show the working tree status
  sync        Update working tree to the latest revision
  upgrade     Check and upgrade git-repo
  upload      Upload changes for code review
  version     Display the version of git-repo

Flags:
      --config string   config file (default is $HOME/.git-repo.yaml)
      --dryrun          dryrun mode
  -h, --help            help for git-repo
  -q, --quiet           quiet mode
      --single          single mode, no manifest
  -v, --verbose count   verbose mode
  -V, --version         Show version

Help of repo

Usage: repo [-p|--paginate|--no-pager] COMMAND [ARGS]

Options:
  -h, --help            show this help message and exit
  --help-all            show this help message with all subcommands and exit
  -p, --paginate        display command output in the pager
  --no-pager            disable the pager
  --color=COLOR         control color usage: auto, always, never
  --trace               trace git command execution (REPO_TRACE=1)
  --trace-python        trace python command execution
  --time                time repo command execution
  --version             display this version of repo
  --show-toplevel       display the path of the top-level directory of the
                        repo client checkout
  --event-log=EVENT_LOG
                        filename of event log to append timeline to
  --git-trace2-event-log=GIT_TRACE2_EVENT_LOG
                        directory to write git trace2 event log to

The most commonly used repo commands are:
  abandon        Permanently abandon a development branch
  branch         View current topic branches
  branches       View current topic branches
  checkout       Checkout a branch for development
  cherry-pick    Cherry-pick a change.
  diff           Show changes between commit and working tree
  diffmanifests  Manifest diff utility
  download       Download and checkout a change
  gitc-delete    Delete a GITC Client.
  gitc-init      Initialize a GITC Client.
  grep           Print lines matching a pattern
  info           Get info on the manifest branch, current branch or unmerged branches
  init           Initialize a repo client checkout in the current directory
  list           List projects and their associated directories
  overview       Display overview of unmerged project branches
  prune          Prune (delete) already merged topics
  rebase         Rebase local branches on upstream branch
  smartsync      Update working tree to the latest known good revision
  stage          Stage file(s) for commit
  start          Start a new branch for development
  status         Show the working tree status
  sync           Update working tree to the latest revision
  upload         Upload changes for code review

You are right. To use git-repo as a replacement for repo, there is still a long way to go.

After publishing my 2nd book next year, I will continue to write new features for this project.