Help us improve the GitPulse documentation. Fill in the survey.

  1. Conclusion

  • For: Thesis reader
  • Requires: Nothing
GitLab holds plenty of data about students’ work, but it is spread across issues, branches, merge requests, discussions, commit history and pipelines. The thesis arranges it by the questions a teacher asks when checking a team project.

Contributions:

  • a decomposition of the course requirements into checks R01 to R13 with a named limit of interpretation,
  • a verified mapping of the checks to GitLab interfaces, including the data that cannot be obtained,
  • the deployed, event-driven GitPulse platform without periodic crawling or changes to student projects, with a classroom assistant behind its own security boundary,
  • an evaluation method with concrete measures and criteria set before measuring.

The first five sub-tasks are done. For the sixth the evaluation method is ready and its execution with the target group follows. The thesis therefore does not yet report time saved, agreement with manual grading or an effect on students.

Open questions remain: how often the system agrees with a teacher on real projects, whether R01 to R13 carry over to differently organised projects, and whether a short explanation of a failed check tells a student what to do. The measurements in winter 2026/2027 and the live deployment from February 2027 will answer them.