Use projectbluefin/common for planned work tracking#587
Merged
Conversation
Replace project board API dependency with repository-based tracking: - Planned work: merged PRs from projectbluefin/common - Opportunistic work: merged PRs from other monitored repos - Filter out closed issues (only include merged PRs) This approach: - Works with standard GITHUB_TOKEN (no project:read scope needed) - Captures ~50% of planned work based on historical data - Removes dependency on organization-level Projects V2 API December 2025 report regenerated with new approach: - 49 planned PRs (was 8, excluded 9 issues) - 78 opportunistic PRs (was 179, excluded 55 issues) - All items now show merged contributions only Refs: #586 (planned vs opportunistic work split)
…highlighting - Add github-actions to bot detection patterns (matches without [bot] suffix) - Update AGENTS.md to document new contributor highlighting: - Listed in separate section above repeat contributors - Gold foil effect (highlight prop) on first contribution - Bot detection patterns updated - Update architecture docs to reflect repository-based approach - Regenerate December report with github-actions filtered out December report changes: - 20 contributors (was 21, github-actions excluded) - 74 opportunistic PRs (was 78, github-actions moved to bot section) - 13 bot PRs (was 9, includes 4 github-actions PRs)
The monthly report scripts were written using ES module syntax (import/export) but broke the build when 'type': 'module' was added to package.json globally. This caused two problems: 1. Existing fetch scripts use CommonJS (require) and failed 2. Docusaurus internals expect CommonJS and failed with require.resolveWeak error Solution: Remove global 'type': 'module' and use .mjs extension only for the monthly report scripts that need ES modules. Fetch scripts remain as .js with CommonJS, preserving the working build. Changes: - Remove 'type': 'module' from package.json (revert fba2f27) - Rename generate-report.js → generate-report.mjs - Rename scripts/lib/*.js → *.mjs (report dependencies) - Update imports to use .mjs extensions - Update package.json npm script to call .mjs file Fixes build failure on main branch and PR #587.
castrojo
added a commit
that referenced
this pull request
Jan 27, 2026
Regenerate January 2026 monthly report to include structural improvements: - Split categories into Planned vs Opportunistic subsections - Use projectbluefin/common for planned work tracking - Separate Focus Area (area/ labels) from Work by Type (kind/ labels) - Apply proper bot filtering and contributor tracking - Fix MDX curly brace escaping in PR titles to prevent build errors Script improvements: - Add --month=YYYY-MM CLI argument for report regeneration - Escape curly braces in PR/issue titles to prevent MDX/JSX parsing errors - Applied fix to all formatItemList functions in markdown generator Previous report was generated before PRs #586 and #587 were merged. This regeneration brings the January report up to date with current format. Fixes MDX build error: "boot is not defined" caused by unescaped curly braces in PR titles like "/{boot,tmp}" being interpreted as JSX. Refs: #586, #587
castrojo
added
github_actions
kind/automation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replace project board API dependency with repository-based tracking for monthly reports:
projectbluefin/commongithub-actionsbot from contributor listsMotivation
The GitHub Actions workflow fails because
GITHUB_TOKENcannot access organization-level Projects V2 (requires Personal Access Token withread:projectscope). This approach eliminates that dependency while capturing the majority of planned work.Data Analysis
Historical data shows
projectbluefin/commoncaptures significant planned work:This is "good enough" tracking without requiring PAT management.
Changes
Script Changes
projectbluefin/commonas planned workgithub-actionsto bot detection patternsDocumentation Updates (AGENTS.md)
highlight={true}prop) on first contributiongithub-actions)Report Changes (December 2025)
/pull/URLs (no/issues/URLs)Testing
✅ Local generation works with
gh auth token✅ Report generated successfully (see
reports/2025-12-31-report.mdx)✅ All items are merged PRs only (no issues)
✅ No
/issues/URLs in report lists✅ Planned work properly sourced from projectbluefin/common
✅ github-actions bot filtered out of contributors
✅ github-actions PRs shown in bot activity section
✅ Contributor tracking accurate (20 human contributors)
Trade-offs
Won't capture:
Will capture:
Next Steps
Refs: #586