grafana/pyroscope

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

Open

#4,392 opened on Aug 25, 2025

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

Repository metrics

Stars
 (9,041 stars)
PR merge metrics
 (PR metrics pending)

Description

Contributor guide

Research direction
Investigate the current implementation of GitHub integration references using mapping JSON, and explore how to replace it with annotations as discussed in PR #3956. Review the linked discussion for context.
Tech stack
c
Domain
backend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40