Skip to content

docs: refresh contributor data - #23

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/update-contributor-leaderboard
Open

docs: refresh contributor data#23
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/update-contributor-leaderboard

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated weekly update of structured organization contributor data.

Changes:

  • Updated profile/core_contributors.json data export

@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch 22 times, most recently from 8682ccd to 0cb1fb6 Compare July 27, 2026 05:54
@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch 4 times, most recently from 299bf8c to 484b60a Compare August 1, 2026 03:20

@ShuhaoZhangTony ShuhaoZhangTony left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这次自动刷新不能直接合并,人员分类出现了两处实质回归:

  1. vllm-ascend-hust-diffspec 仍被列为核心仓库,导致仅向该仓库提交的杜忠承进入核心成员。DiffSpec 是外部课题,当前不属于 vLLM-HUST 核心成果链,应从 core_repo_names 和核心资格计算中移除。
  2. 刘世峰(Remygred)从核心成员被降到参与人员,生成结果只保留 survey 仓库;但 vllm-hust main 仍能查到他以 Remygred 身份提交的 d4a408c4743e3b77a79cccb5228d93fe。这是贡献采集或归并回归,不能用本次快照覆盖现有正确数据。

请先修正生成脚本的核心仓库集合与 commit/alias 采集,再重新生成。校验脚本应新增两个不变量:DiffSpec-only 贡献者不得进入核心成员;Remygred 的 vllm-hust 历史提交必须归并到刘世峰并保持核心资格。

@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch 3 times, most recently from d9d06cc to 32beabf Compare August 3, 2026 05:41
@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch 2 times, most recently from 926f024 to de52b8b Compare August 3, 2026 09:50

@ShuhaoZhangTony ShuhaoZhangTony left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这次自动刷新仍未处理上次的两个不变量,不能合并。当前生成文件中,dzcixy 仍只有 vllm-ascend-hust-diffspec 一个仓库,却被标记为 core_repository_contributor=true、core_member=true;Remygred 仍只统计 survey 仓库的 6 个提交,core_repository_contributor 和 core_member 都是 false,vllm-hust 的历史提交没有归并进来。请先修生成器的核心仓库集合和 alias/commit 采集,并加入对应回归校验,再重新生成;单纯刷新快照不会解决分类错误。

@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch from de52b8b to 003adb0 Compare August 4, 2026 06:57

@ShuhaoZhangTony ShuhaoZhangTony left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已按当前 003adb0 重新核对,两个分类问题都还存在:dzcixy 仍只有 vllm-ascend-hust-diffspec 这一项,却被标记为 core_repository_contributor=true、core_member=true;Remygred 仍只统计 survey 仓库 6 个提交,vllm-hust 历史提交没有合并,两个 core 标记仍是 false。这个提交仍然只是重新生成错误快照,请先修生成器的核心仓库集合与身份 alias/commit 归并,并用这两个账号做回归校验。

@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch from 003adb0 to 489fbe7 Compare August 5, 2026 09:37

@ShuhaoZhangTony ShuhaoZhangTony left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

489fbe7 仍然没有解决前几轮指出的两个分类问题:

  • dzcixy 仍只包含 vllm-ascend-hust-diffspec 的 1 个提交,但 core_repository_contributorcore_member 都是 true;
  • Remygred 仍只统计 survey 仓库的 6 个提交,vllm-hust 历史提交没有归并,两个 core 标记仍是 false。

这次仍是重新生成错误快照,不能合并。请先修正生成器的核心仓库集合与身份 alias/commit 归并,并加入这两个账号的回归校验后再刷新数据。

@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch 3 times, most recently from c3eb74c to eee15b4 Compare August 7, 2026 02:19
@github-actions
github-actions Bot force-pushed the automation/update-contributor-leaderboard branch from eee15b4 to cfcd515 Compare August 10, 2026 04:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant