grafana/pyroscope

Consider using Annotations for storing github integration references instead of Mapping json

Open

#4392 opened on Aug 25, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C (9,041 stars) (528 forks)batch import
good first issuestorage

Description

https://github.com/grafana/pyroscope/pull/3956#discussion_r1975245891

Contributor guide

Tech stack
gogithub actions
Domain
backenddevops
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingGitHub API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the discussion at PR #3956 (link in issue) to understand the current mapping JSON approach and the proposed annotation based alternative. Examine the relevant code files for GitHub integration references, likely in GitHub related packages. The issue suggests a refactoring to use annotations instead of a mapping JSON, so you need to assess feasibility and plan the changes. No existing PR or assignee, so this is available for a newcomer with Go experience.