SETTING UP REPOSITORY SMARTGIT UPDATE

Journal view To push a range of commits up to a certain commit,.Branches view In the context menu of the Branches view, youĬan invoke Push and Push To on local branches.Repositories view by selecting the open repository and choosing Repositories view You can invoke Push in the.The thirdĬommand is only enabled if the Journal view is focused. Toolbar buttons, depending on your toolbar configuration. Menu and toolbar In the menu, you can invoke the various PullĬommands with Remote|Push, Remote|Push To and.

The Push commands listed above can be invoked from several places in The tracking will not be configured if the git option fault Receive changes from the remote repository and make use of Git’s branchĬontains an option to avoid this dialog and always configure the In mostĬases it is recommended to set up tracking, as it will allow you to Whether to set up tracking for the newly created remote branch. If you try to push commits from a new local branch, you will be asked Journal view, rather than all commits, in the current branch to

Push Commits pushes the selected range of commits from the.

You canĪlso invoke Push To on a remote to push (or synchronize) allīranches from the selected remote to another remote. Which is considered by SmartGit’s forced push detection). Not when pushing to the primary remote repository (i.e. Repository for which forcing the push may be necessary while it is This is necessary when pushing to a secondary remote To command always allows to do a forced push, what can beĬonvenient. Multiple repositories have been set up, the Push To dialog willĪllow you to select the remote repository to push to. With the Push ToĬommand you can only push to one remote repository at a time. Matching branch, or to a ref specified by name. Push To pushes all commits in the current branch either to its.SmartGit will detect automatically whether a forced Push command you can push to multiple repositories in a single Push pushes all commits of the current branch (or the selectedīranch in the Branches view) to its tracked branch.send) your localĬommits to one or more remote repositories. The various Push commands allow you to push (i.e. Pulled commits: are part of your HEAD’s history and theirĬontents are present in your working tree.Such commits in the Log and perform various operations on it,Įspecially you can Merge or Rebase onto such a commit or Fetched commits: are already present in the local repository,īut not yet part of your HEAD’s history.Them, it’s usually safe to fetch them using Remote|Pull Want to know more details about these commits and/or investigate These commits, not even the number of “incoming” commits. SmartGit does not have more information on In the local repository for a specific branch, it is considered to Light-weight operation which only reports remote repository branches Such commits, SmartGit uses a git ls-remote which is a In the Preferences, section Background commands. Repositories view if Detect remote changes has been selected SmartGit will denote such kind of “incoming”Ĭommits by displaying a green arrow for the repository’s node in the Remote-Repository-Only commits: are not yet present in your.Regarding the presence in your repository/working tree you canĭistinguish between three kinds of commits:

SETTING UP REPOSITORY SMARTGIT UPDATE

Updated as well, select Update existing and fetch new tagsįrom More Options. Update possibly changed tags from the remote repository. Want to “preserve” these merge commits during the rebase or flatten theīy default, Git (and hence SmartGit) will only pull new tags, but don’t When rebasing, SmartGit will detect whether there are local mergeĬommits which have to be rebased and in this case ask you whether you In that case SmartGit will leave the repository inĪ merging or rebasing state so you can either resolve the conflicts If a merge or rebase is performed after pulling, it may fail due toĬonflicting changes. The Pull dialog allows you to set your choice as default for the current These options are meaningless, if you select to Fetch In the latter case, you can merge or rebase by hand, as SmartGit will do after the commits have been fetched: Merge the localĬommits with the fetched commits or rebase the local commits onto theįetched commits. This will open the Pull dialog, where you can specify what Use Remote|Pull (or the corresponding toolbar button) to invoke the In the remote branches, and optionally ‘integrates’ (i.e. The Pull command fetches commits from a remote repository, stores them Synchronize command that combines pulling and pushing. Pulling from and pushing to the remote repositories. Synchronizing the states of local and remote repositories consists of Propose Changes Synchronizing with Remote Repositories

Setting up repository smartgit