cg-update - fetch and merge changes from a remote repository
cg-update [-f] [--squash] [-v] [BRANCH_NAME]
Takes the branch name as an argument, defaulting to origin or the current branch's default remote branch, see cg-fetch(1) for details.
This is similar to running cg-fetch and cg-merge commands successively. Please refer to the documentation of those commands for more details about the operation. Note that if you are not doing own development but only following some project, it is recommended to use this command instead of cg-fetch(1) + cg-merge(1) since cg-update(1) can handle some additional corner cases (in particular, if the remote branch rebases, cg-update(1) will fast-forward instead of doing a tree merge and diverging).
Note that in the GIT newspeak, the operation being performed by cg-update is now called pull, even though in the past and in many other version control systems systems, pull is the name for the operation performed by cg-fetch(1). Please do not let this confuse you. (Cogito won't call this update operation pull, since about everyone but GIT and BK users uses it in the fetch meaning.)
Force the complete fetch even if the heads are the same.
"Squash" merge - condense all the to-be-merged commits to a single merge commit. This is not to be used lightly; see the cg-merge documentation for further details.
Display more verbose output - most notably list all the files touched by the pulled changes.
Print usage summary.
Print user manual. The same as found in cg-update(1).
Print Cogito version.
Additional flags to pass cg-fetch (useful e.g. for -v -v).
Copyright © Petr Baudis, 2005