GIT Plugin/en

Introduction

The plugin provides git-functionality for testsuites.

For proper work you need a remote-repository and access to it without entering user name and password.

Before starting a git-command, that affects your testsuite-files, a copy of these files will be created. They become the suffix ".last.sav".

The git-functionality will not work, if you use sub-directories in your project. The .git-directory must be in the same directory as your files of the testsuites.

Initialization

Configuration

Sets the global git parameters for user name and mail-address in the [[[Datei:http://www.example.com Link-Text]]].

 Executed git-command: git config --global user.name=<user name>, 
                       git config --global user.email=<mail address>.

Clone a repository

Provides the functionality of 'git clone': Cloning a repository into a a new local directory. A dialog box asks for the url of the remote repository.

 Executed git-command: git clone <repository-url>.

Adding and Committing

Add

Before you can commit your new or changed testsuite, you have add the file to the git index.

 Executed git-command: git add <testsuite>.

Unstage

Removes an added testsuite from index. It is still modified, but not destined for commit.

 Executed git-command: git reset HEAD <testsuite>

Add All and Commit...

Adds all modified files and commits them in one step. You will be asked for entering a commit-message.

 Executed git-command: git commit -a -m "<commit-message>"

Commit..

Commits all added files. A message-box will appear to enter the commit-message. An empty commit-message is not allowed.

 Executed git-command: git commit -m "<commit-message>"

Commit (amend)

Replace the tip of the current branch by creating a new commit. The new commit has the same parents and author as the current one.

You should understand the implications of rewriting history if you amend a commit that has already been published!

 Executed git-command: git commit --amend.

Discard changes in working directory

If you get conflicts by changing the branch, because of uncommitted changes in some of your files, you can discard the changes.

Attention: Your changes are lost!

The other possibility is to commit your changes.

 Executed git-command: git checkout -- <testsuite>.

Branches

Create Local Branch...

Creates a new local branch with a given name.

 Executed git-command: git checkout -b <branch>.

Delete Local Branch...

Deletes a local branch.

The branch must be merged into the current branch. Otherwise the deletion will be refused.

 Executed git-command: git branch -d <branch>.
 

Checkout Branch...

Checks out a branch. In a dialog box you can choose the desired branch.

If you have uncommitted changes, git rejects the checkout of the new branch. You can discard (see below) or commit your changes and try again.

 Executed git-command: git checkout <branch>.

Push

To publish your test-suites to the remote-repository you have to push it.

 Executed git-command: git push.

Pull

Incorporates changes from the remote repository into the current branch.

Because automatically merge by git isn't possibly, you can get merge-conflicts. To avoid this, better use Merge. If you get unresolvable conflicts, you can reset the files wit Merge Abort after Conflict and try again with Merge.

 Executed git-command: git pull.

Comparing and merging

Fetch

Downloads objects and refs from the remote repository, but don't change the local files.

 Executed git-command: git fetch.

Merge

Merges with HEAD of the current branch. (Only possible on remote-branches.)

You get the newest version of the current branch from the repository with the changes done by others. If there exists not automatically mergeable differences between the two version the Expecco-ProjectDifferenceBrowser will open and you can take over your changes.

 Executed git-command: git fetch                   
                       git merge      

Merge with Branch...

Merges the contents from another branch, you select in a dialog box, to your testsuites.

This command doesn't change the branch in your working directory.

 Executed git-command: git fetch
                       git merge <branch>

Merge Commit

You can finish the merge with a final 'Merge Commit. You maybe override changes from others.

 Executed git-command: git commit -a --no-edit

Merge Abort after Conflict

If you have unresolvable conflicts after pulling, you can abort the merge. You can retry the merge with Merge.

 Executed git-command: git merge --abort

Status information

Show Log

Displays a dialog box with the commit log of the current branch.

 Executed git-command: git log

Show Status

Shows the working tree status.

 Executed git-command: git status

Not implemented

• Drop branches.
• Use of the git-stash-command.

---

Copyright © 2014-2024 eXept Software AG