Files

63 lines
2.3 KiB
YAML

name: Update Contributors
on:
schedule:
- cron: "0 18 * * 0"
workflow_dispatch:
permissions:
contents: write
concurrency:
group: contributors
cancel-in-progress: true
jobs:
update:
runs-on: ubuntu-latest
steps:
# main 的 ruleset 要求改动走 PR,默认 GITHUB_TOKEN 直推会被 GH013 拒掉;
# 用 owner PAT 后 push 以 admin 身份命中 ruleset 的 bypass(同 mcp-release.yml)。
- uses: actions/checkout@v5
with:
token: ${{ secrets.MCP_RELEASE_TOKEN || secrets.PROJECT_AUTOMATION_TOKEN }}
- name: Verify push token
# 快照抓取要打好几页 GitHub API,先用一步廉价检查把缺 token 的情况挡在前面,
# 否则要等到最后 push 才以 GH013 报错,很难看出是令牌问题。
env:
PUSH_TOKEN: ${{ secrets.MCP_RELEASE_TOKEN || secrets.PROJECT_AUTOMATION_TOKEN }}
run: |
if [ -z "$PUSH_TOKEN" ]; then
echo "::error::No owner PAT configured; the default GITHUB_TOKEN cannot push to the protected main branch."
exit 1
fi
- uses: actions/setup-node@v6
with:
node-version: 22
- uses: pnpm/action-setup@v6
- name: Refresh contributor activity
working-directory: docs
run: pnpm contributors:update
env:
GITHUB_TOKEN: ${{ github.token }}
- name: Commit refreshed snapshot
run: |
if git diff --quiet -- docs/data/contributors.json; then
exit 0
fi
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git add docs/data/contributors.json
git commit -m "chore(docs): refresh contributor activity"
# 抓取快照要跑十几分钟,期间 main 被其它合并推进时直推会被拒(fetch first)。
# 先 rebase 到最新 main 再重试,避免每天定时任务留下一个红 run。
for attempt in 1 2 3 4 5; do
if git push; then
exit 0
fi
echo "::warning::push attempt ${attempt} was rejected; rebasing onto origin/main"
git pull --rebase origin main
done
echo "::error::Unable to push the refreshed contributor snapshot after 5 attempts."
exit 1