Pick a branch for code coverage branch

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Problem to solve

Having historical data for code coverage values of /master (#33743 (closed)) solves a problem for many developers but not all workflows. Some users work on several long lived branches and want to see and track how code coverage is changing in that branch as well.

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)

Further details

Use Cases

  • When Delaney is planning tech debt issues for the team, they want to know if code coverage of the /development branch is trending up or down, so they can make informed choices about tech debt/stability/features.

Proposal

Add to the graph for code coverage ability to change branches within a project and display the data.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Edited Sep 08, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading