Repository navigation
Conversation
🚫 This PR is missing its before/after evidenceYou attached something, but not one under each heading. Both are required, and they have to sit under their own heading so a reviewer can tell which is which.
How to fix it: edit the description, keep the A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine. Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the |
|
@chaitanyagiri The requested evidence is now attached under I reproduced the workflow parser against the current PR body. In A minimal fix is to replace that alternative with a true end-of-string check, for example Failed run: https://github.com/chaitanyagiri/munder-difflin/actions/runs/32628110810 |
…ward or 4) RELEASE.md contradicted itself: line 16 said "four merged pull requests" (only tonight's four integration merges), the Thanks said "23 community pull requests landed in this release" (the 0.4.5 number copied forward), and the historical tail correctly says those 23 landed in v0.4.5. Recounted from the actual 0.4.6 changeset (main b9f34e7..release tip, linear so it is exactly this release). Method: a community PR is one authored by someone other than the founder (@chaitanyagiri) whose work landed here, whether merged or re-implemented. That gives 16 community PRs from 13 contributors: #156 #205 #213 #225 #242 #243 #248 #270 #271 #282 #284 #286 #310 #317 #323 #339. Fifteen landed as merges; #213 (Arabic) landed by re-implementation, which is why a merge-only count returns 15 and misses it. Line 16 and the Thanks now both say 16, the Thanks names all 13 contributors inline so the credit matches the count, and the 0.4.5 sections (its intro and its historical table) are left at 23 untouched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LDbmAwrgtGskFGCRkYZBx4
|
Shipped in v0.4.6. Your commit This closes rather than shows as merged because the commit went in through the 0.4.6 release branch instead of this PR's branch. https://github.com/chaitanyagiri/munder-difflin/releases/tag/v0.4.6 Apologies for the delay in closing it. Thank you. |
|
Hi, @chaitanyagiri , |
|
Hey, @jhinzzz thanks for your contribution, apologies for not marking it as merged, I've added a discussion thread explaining the issue. I've added the credits for this one in the release notes. Your contributions are very valuable to us, please rest assured that next PRs will be marked as merged or handles will be tagged for contributions in readme or a dedicated contributors markdown file. Best, |
What & why
Munder keeps each Codex worker in an isolated
CODEX_HOME, while usage scanners normally read only the standard user-level.codex/sessionsand.codex/archived_sessionsroots. As a result, valid worker rollouts were invisible to external usage reports.This change:
munder-difflin/<hive>/<agent>directory under the standard Codex scan rootsCODEX_HOME, preserving existing resume and ownership pathsRollout files are neither transformed nor duplicated.
Type of change
Screenshots / clips
Before
After
Discord (optional)
Discord:
Checklist
npm run typecheckpasses (the de-facto CI gate).npm run buildsucceeds.DESIGN.md/tokens.ts— no UI changes.ATTRIBUTION.md— no art added.Verification
npm run test:focused: 244 passed, 0 failed