You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Pk-vcs-git is lightweight library for execute basic Git VCS operations (merge, b
10
10
- Folder where vcs-related operations are executed. Provides thread- and process-safe repository of working folders. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
11
11
- Test Repository
12
12
- Git repository which is used to execute functional tests
13
-
- Hosted on [Github](https://github.com/) using username and password provided by enviroment variables (see below)
13
+
- Hosted on [Github](https://github.com/) using username and password provided by environment variables (see below)
14
14
- Generates new before and deletes after each test
15
15
- Named randomly (uuid is used)
16
16
-[Kohsuke Github API](http://github-api.kohsuke.org/) is used as to work with Github API
@@ -45,7 +45,7 @@ Pk-vcs-git is lightweight library for execute basic Git VCS operations (merge, b
45
45
IVCS vcs =newGitVCS(repoWorkspace);
46
46
```
47
47
- Use methods of `IVCS` interface. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
48
-
- Use `vcs.setProxy()` and `vcs.setCredentials()` if neccessary
48
+
- Use `vcs.setProxy()` and `vcs.setCredentials()` if necessary
49
49
50
50
# Implementation details
51
51
-[JGit](https://eclipse.org/jgit/) is used as framework to work with Git repositories
@@ -58,11 +58,11 @@ Pk-vcs-git is lightweight library for execute basic Git VCS operations (merge, b
58
58
# Functional testing
59
59
- Github is used for hosting the Test Repository
60
60
-[Kohsuke Github API](http://github-api.kohsuke.org/) is used to create and delete Test Repository
61
-
-`PK_VCS_TEST_GITHUB_USER`enviroment var or JVM var is used as username for access to Github
62
-
-`PK_VCS_TEST_GITHUB_PASS`enviroment var or JVM var is used as user password for access to Github
61
+
-`PK_VCS_TEST_GITHUB_USER`environment var or JVM var is used as username for access to Github
62
+
-`PK_VCS_TEST_GITHUB_PASS`environment var or JVM var is used as user password for access to Github
63
63
- New Test Repository is created before each test and deletes automatically after each test
64
64
- To execute tests just run GitVCSTest class as JUnit test. Tests from VCSAbstractTest class will be executed. See [pk-vcs-test](https://github.com/ProjectKaiser/pk-vcs-test) for details
65
-
- NOTE: Github has some latency for exposing results of previosly executed operations. For example if create a new branch and immediately check branches list then Github could return old branches list. Need to wait a couple of second to get new list. So if a test failed then try to execute it again.
65
+
- NOTE: Github has some latency for exposing results of previously executed operations. For example if create a new branch and immediately check branches list then Github could return old branches list. Need to wait a couple of second to get new list. So if a test failed then try to execute it again.
66
66
67
67
# Limitations
68
-
- Commit messages can not be atached to branch create and delete operations because Git does not exposes these operations as separate commits
68
+
- Commit messages can not be attached to branch create and delete operations because Git does not exposes these operations as separate commits
0 commit comments