Repository navigation
chore(mcp): glama.json 移到仓库根目录并声明 maintainers,解锁 Glama 认领 - #511
Conversation
… Glama's claim flow reads it
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
外部清单收录 PR(punkpeye/awesome-mcp-servers#14974)卡在最后一步:仓库主人 punkpeye 要求先在 Glama 完成两件事——认领服务器、生成质量评分——才合并。而 Glama 对组织名下服务器的认领流程(认领弹层 FAQ 原文)要求:
现状问题
glama.json一直躺在mcp/子包里(当时随 Glama 提交一起放进包内),认领流程只读仓库根目录,读不到author,没有maintainers—— 组织仓库不声明 maintainers,所有权验证无从谈起,Glama 页面始终显示未认领改动
git mv mcp/glama.json glama.json(git 按 rename 识别,其余元数据一字未动);影响面
src/,无需npm run sync;纯元数据搬移,无行为变更,不配新测试;mcp/package.json没有files清单锁,glama.json本也不属于 npm 包语义——Glama 只从 GitHub 仓库根目录读它;mcp/glama.json这条路径(仅 CHANGELOG 提过一次 glama 提交);Summary by CodeRabbit
modusensus列为维护者。