Fix contributor attribution for GSA checks#2003
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (15)
📝 WalkthroughWalkthroughRegenerates Maester documentation for MT.1187–MT.1195, updates test and contributor indexes, links MT.1186 metadata to command documentation, and runs generated-doc validation in the website build workflow. ChangesMaester documentation regeneration
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
Deploying maester with
|
| Latest commit: |
8512ac0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8e23b2a9.maester.pages.dev |
| Branch Preview URL: | https://codex-fix-contributor-attrib.maester.pages.dev |
Summary
Root cause
The contributor feature (#1999) and its fallback snapshot merged before #1992. PR #1992 then squash-merged as commit
28cd9bfe, correctly authored byChristopher Brumm <30894952+crmhh@users.noreply.github.com>. The identity resolver handles that noreply address directly, but the committed snapshot still ended at MT.1186. Shallow-clone website deployments therefore used the old snapshot and omitted Christopher even though full-history generation produced the right attribution.Validation
node scripts/generate-test-docs.mjs --checkunder Node 24npm run buildDocusaurus production buildcrmhhowns MT.1187–MT.1195 incontributors.jsongit diff --checkNo blog migration files are changed.
Summary by CodeRabbit
New Features
Documentation
Tests