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

描述

贡献者指南

技术栈

gogithub actions

领域

backenddevops

议题类型

refactor

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

half day

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

mostly clear

前置要求

Go programmingGitHub API

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

60

研究方向

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.