Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #50299
Closed (moved) (moved)
Open
Created Aug 14, 2018 by Job van der Voort@JobV🚀Contributor

Line-specific information API

Problem to solve

Linters, specs, security tests, all display information specific to one of more lines. This should be visible when you look at any particular file in GitLab, but isn't now.

Further details

Code coverage in files is one of the most requested features. This is towards showing that, among other things.

Proposal

An API that allows you to attach any information to any particular line or lines of any file, or diff (this should work in MR)

This would allow our internal tools, but also external tools, to report directly in files which line does or doesn't meet particular criteria, is problematic, or otherwise worthy highlighting.

On top of files, you should be able to control what information is highlighted (e.g. which lines are blue/green/red). By clicking on any line with information, you should be able to see all warnings / messages / information for that line.

This includes:

  • code quality
  • code coverage
  • security warnings
  • test failure
  • linter information

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

TBD

(If no way to measure success, link to an issue that will implement a way to measure this)

Links / references

Assignee
Assign to
Time tracking