DB Issues

[Nyzabes]

• File: webUrl broken:
  URLs for older files refer to an URL for the current branch.
  Example: yarn.lock, which does not exist in the project anymore, refers to .../blob/feature/102/... if DB was constructed on branch feature/102.
  --> The webUrl leads to a 404 page.
• use the (currently empty) commits-stakeholders connection instead of the signature attribute in commits
• use the (currently empty) issues-commits connection instead of the mentions attribute in issues
• use the issues-stakeholders connection instead of the author/assignee/assignees attributes in issues
• use the commits-commits connection instead of the parents/history attributes in commits
• add branches-commits connection instead of using the branch attribute in commits
• add commits-builds connection instead of using the sha/ref attributes in builds
• add builds-stakeholders connections instead of using the user/userFullName attributes in builds
• rename collections according to edge direction (for example: stakeholders-commits instead of commits-stakeholders since in this collection, _from points to stakeholders and _to points to commits)

[uberroot4]

Is it on purpose that each collection as e.g. commits-stakeholders is read from right to left (from-entry references stakeholders, to-entry references commits). One might would assume that the reading direction left to right would also be the direction of the edge (commits->stakeholders). As it is the same for all edge collections I investigated, we should consider simply renaming them

[Nyzabes]

@uberroot4 You're right, I added it as a Todo.