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
@@ -228,9 +228,9 @@ enhance the data further with relationships between artifacts and packages.
228
228
229
229
Be aware that this script deletes all previous relationships and nodes in the local Neo4j Graph database.
230
230
231
-
### Import git log
231
+
### Import git data
232
232
233
-
Use [importGitLog.sh](./scripts/importGitLog.sh) to import git log data into the Graph.
233
+
Use [importGit.sh](./scripts/importGit.sh) to import git data into the Graph.
234
234
It uses `git log` to extract commits, their authors and the names of the files changed with them. These are stored in an intermediate CSV file and are then imported into Neo4j with the following schema:
235
235
236
236
```Cypher
@@ -256,7 +256,7 @@ Here is the resulting schema:
256
256
257
257
#### Parameter
258
258
259
-
The optional parameter `--repository directory-path-to-a-git-repository` can be used to select a different directory for the repository. By default, the `source` directory within the analysis workspace directory is used. This command only needs the git history to be present so a `git clone --bare` is sufficient. If the `source` directory is also used for the analysis then a full git clone is of course needed (like for Typescript).
259
+
The optional parameter `--source directory-path-to-the-source-folder-containing-git-repositories` can be used to select a different directory for the repositories. By default, the `source` directory within the analysis workspace directory is used. This command only needs the git history to be present. Therefore, `git clone --bare` is sufficient. If the `source` directory is also used for code analysis (like for Typescript) then a full git clone is of course needed.
0 commit comments