Navigating Git repository data

If your project employs GitHub integration, the project menu on the lefthand side of the screen with have a menu item named "Code repositories. This leads to a screen with the following three tabs:

The "Code repositories" tab provides access to all the team's repositories. The "My commits" shows a list of all commits that could be attributed to you, either as the person who created the commit or a collaborator of the committer. The "Collaborations" tab lists all collaborative coding sessions you have participated in and enables you to register additional ones.

Code repositories

This tab shows a list of the repositories your team is using for this project. Usually, you will only need one but you can link as many as needed. You can add or link additional repositories. It is possible to examine the details of a specific repository or view a list of the commits of an existing repository. This page also provides instructions for cloning each of the team's remote repositories.

The initial page shows three charts summarising the activity on the repository:

  1. The Commit activity chart shows the number of commits per day in all of the repositories. This gives an indication of the amount of coding activity per day.
  2. The Additions, deletions and changes chart shows the number of line additions and line deletions per day in all of the team's repositories. This chart also provides an indication of the amount of coding activity per day. Note that some commits, deemed to be outliers are not included in this chart.
  3. The Activity accounted for chart consists of four pie charts that visualises the proportion of the team's coding activity that Team Feedback could attribute to team members. Here, coding activity is measured by the number of commits on the default (master) branch, the number of line changes on the default (master) branch, the number of commits in the entire repository and the number of line changes in the entire repository. If these pie charts do not show that 100% of the code is accounted for, there are commits that Team Feedback could not attribute to a team member.

These charts are also provided per repository. You can find it by selecting a specific repository.

My commits

Under this tab, you can find a list of the commits that have been attributed to you. Commits can be attributed to you in two ways: as the person who created the commit or as a person who collaborated with the committer at the time the committer created the commit. The former type of attribution requires that Team Feedback is able to identify you as the committer. The latter requires that the committer can be identifies by Team Feedback and that the committer registered a code collaboration with you at the time of the commit.

Collaborations

A collaborative coding session is considered to be a session where two or more people work on the same code from the same machine. While coding collaboratively, all commits will be in the name of one person (the committer), who will receive credit for the code developed collaboratively. To ensure that the other team members also receive credit the code that was developed collaboratively, the committer must register the collaborative coding session using this form immediately after the end of the session so that all participants receive credit for the code.

Under the Collaborations tab, you find a list of code collaborations you were involved. Here, you can create new collaborations, edit existing collaborations (within certain time limits), delete existing collaborations (with certain time limits) and view the details of a collaborative coding session.