fix: Dashboard note persistence for external Action users#84
Conversation
Why Dashboard persistence ran git from the npm --prefix package directory. Remote Action installations execute there without a .git directory, so same-repository pull requests failed before updating gh-pages. User impact Repositories using wasabeef/AgentNote@v1 with Dashboard mode can persist pull request notes to gh-pages. Local uses of the Action continue to work. Verification npm test --prefix packages/dashboard npm run build --prefix packages/dashboard npm run build --prefix packages/cli npm run typecheck --prefix packages/cli npm run lint --prefix packages/cli npm test --prefix packages/cli Release note: Dashboard note persistence now works when Agent Note is used as a remote GitHub Action.
|
Warning Review limit reached
Next review available in: 46 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ 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 |
wasabeef
changed the title
Why External Action checkouts also ran Dashboard restore and sync git commands from the npm package directory. Those failures were swallowed, leaving an empty snapshot that persistence could commit over existing PR notes. User impact Remote Action users now restore, generate, and persist real Dashboard note data from the checked-out repository without risking deletion from an empty snapshot. Verification npm test --prefix packages/dashboard npm run build --prefix packages/dashboard npm run build --prefix packages/cli npm run typecheck --prefix packages/cli npm run lint --prefix packages/cli npm test --prefix packages/cli Release note: skip
1 participant
Summary
Root cause
npm --prefix changes each workflow script cwd to the Dashboard package. For remote Action consumers, that package lives under _actions and has no .git directory. Persistence crashed at git worktree add, while restore and sync swallowed their git failures and produced an empty snapshot.
User impact
Repositories using wasabeef/AgentNote@v1 with Dashboard mode can restore, generate, and persist actual pull request note data to gh-pages. The fix also prevents an empty snapshot from deleting previously persisted PR notes. Local uses of the Action continue to work.
Validation
Closes #81
🧑💬🤖 Agent Note
Total AI Ratio: —
Agent Note data: No tracked commits
4cb1975fix(dashboard): persist notes from external action checkouts82a5e6afix(dashboard): run all note workflows from workspace