Handbook for teachers¶
Welcome to the GitPulse Teacher's Guide. This section will help you effectively use the tool for monitoring and evaluating student teamwork.
Contents of the manual¶
Here we go¶
First steps with GitPulse - creating a course, adding projects, basic configuration.
Interpretation of results¶
How to correctly interpret compliance scores and identify problems.
Quick overview¶
What does GitPulse offer teachers?¶
| Function | Benefit |
|---|---|
| Automatic Metrics | Objective assessment without manual work |
| Real-time monitoring | Early identification of problem teams |
| Gaming detection | Detecting suspicious behavior |
| Exports and reports | Materials for evaluation and discussion |
| Historical trends | Monitoring the development during the semester |
Typical workflow¶
flowchart LR
A["Create course"] --> B["Add projects"]
B --> C["Configure webhooks"]
C --> D["Monitor"]
D --> E["Identify problems"]
E --> F["Intervene"]
F --> D
D --> G["Grade"]Time requirement¶
| Activity | Without GitPulse | With GitPulse |
|---|---|---|
| Checking team activity | 15-20 min 2-3 min | |
| Identification of inactive | 30+ min immediately | |
| Preparation of materials for the interview | 20 min 5 min | |
| Report generation | 1+ hour | 1 click |
Saving time
According to pilot measurements, GitPulse saves teachers 30-50% of time when evaluating teamwork.
Prerequisites¶
Before starting work with GitPulse you need:
- School GitLab account (git.kpi.fei.tuke.sk)
- Students' GitLab projects (or access to create them)
- GitLab Personal Access Token with rights
api,read_repository - Basic understanding of GitLab workflow (commits, MR, issues)
Gaining access
A GitPulse account is created automatically on first login via the school GitLab (OAuth). If you need a role change (e.g. promoted to instructor), contact the administrator at mykyta.olym@student.tuke.sk.
Additional resources¶
- GitLab integration - Technical details of the setup
- Security - How student data is protected
- API documentation - For advanced use