Understanding Metrics¶
GitPulse evaluates your project using 13 compliance rules (R01-R13). Each rule tracks a specific aspect of team collaboration and DevOps practices.
Rules Overview¶
| Rule | What it tracks | Why it matters |
|---|---|---|
| R01 | Commit regularity | Consistent work instead of last-minute rushes |
| R02 | Team work distribution | Every team member contributes |
| R03 | Issue usage | Task planning and tracking |
| R04 | Commit-issue linking | Traceability of changes |
| R05 | Merge requests and code review | Code quality through peer review |
| R06 | CI/CD pipeline | Automated testing |
| R07 | Pipeline success rate | Pipeline passes without errors |
| R08 | README and documentation | Project documentation |
| R09 | Branch strategy | Using branches (feature branches) |
| R10 | Commit message quality | Meaningful and structured messages |
| R11 | Commit size | Smaller, focused commits |
| R12 | Time distribution | Work is not only in the last few days |
| R13 | Overall team dynamics | Balanced team collaboration |
Compliance Score¶
Your overall compliance score is a weighted average of all rules. The instructor determines the weights for each rule based on the course focus.
Score Levels¶
| Level | Score | Meaning |
|---|---|---|
| Excellent | 80-100% | Team follows all key practices |
| Adequate | 50-79% | Some areas need improvement |
| Insufficient | 0-49% | Significant collaboration gaps |
Rule Details¶
R01 - Commit Regularity¶
What the system checks
Distribution of commits over the tracked period. Ideally, you should commit regularly (e.g., several times per week).
How to improve:
- Commit smaller changes more frequently
- Don't wait until the last day before the deadline
- Break large tasks into smaller parts
R02 - Team Work Distribution¶
What the system checks
The ratio of contributions from individual team members. Every member should contribute meaningfully.
How to improve:
- Distribute tasks evenly among team members
- Use GitLab issues to assign tasks
- Check the contribution overview on the dashboard
R03 - Issue Usage¶
What the system checks
Creation and management of issues in the project. Issues should cover planned tasks.
How to improve:
- Create an issue for every major task
- Use labels for categorization
- Close issues after completion
R04 - Commit-Issue Linking¶
What the system checks
References to issues in commit messages (e.g., #123 or Closes #123).
How to improve:
- Reference issue numbers in commit messages:
feat: add login form (#42) - Use keywords:
Closes #42,Fixes #42,Resolves #42
R05 - Merge Requests and Code Review¶
What the system checks
Use of merge requests and involvement of other team members in review.
How to improve:
- Work on feature branches, not directly on
main - Create merge requests for integrating changes
- Review your colleagues' code before merging
- Add meaningful comments during review
R06 - CI/CD Pipeline¶
What the system checks
Presence and configuration of CI/CD pipeline in the project (.gitlab-ci.yml).
How to improve:
- Create a
.gitlab-ci.ymlfile in the root directory - Set up at least one build and test stage
- Make sure the pipeline covers main branches
R07 - Pipeline Success Rate¶
What the system checks
The ratio of successful to failed pipeline runs.
How to improve:
- Fix failed pipelines as soon as possible
- Run tests locally before pushing
- Don't ignore failed builds
R08-R13 - Additional Rules¶
Rules R08-R13 track additional aspects such as documentation, branch strategy, commit message quality, commit size, time distribution, and overall team dynamics. The principle is always the same - following established DevOps best practices.
Frequently Asked Questions About Metrics¶
Can I see how my score is calculated?
Yes, on the dashboard click on the compliance score to see a breakdown by individual rules including weights.
Why do I have a low score even though I worked a lot?
The compliance score evaluates collaboration practices, not code volume. Even if you wrote a lot of code, missing issues, no merge requests, or uneven work distribution in the team can result in a low score.
When does the score update?
The score updates automatically after each GitLab synchronization, typically within a few minutes after a push or other action.
Does the compliance score directly translate to my grade?
Not necessarily. The compliance score serves as input for the instructor, who decides the final evaluation. The instructor may also consider additional factors.