Repository navigation
chore(pm): sync GitHub issues (gated) - #145
github-actions[bot] wants to merge 2 commits into
Conversation
|
PR author is in the excluded authors list. |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis gated synchronization imports the GitHub issue about the failing Daily Release workflow into the project tracker, records its provenance/history, and links it from the Unreleased changelog without directly modifying main. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 2 issues
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="CHANGELOG.md" line_range="7" />
<code_context>
+
+### Fixed
+
+- Daily Release workflow is failing ([pm-beads-github-be8d2d927676-85](https://github.com/unbraind/pm-beads/blob/main/.agents/pm/issues/pm-beads-github-be8d2d927676-85.toon))
+
## 2026.10.5 - 2026-10-05
</code_context>
<issue_to_address>
**Resolved issue appears upcoming**
When the sync imports the GitHub issue closed on 2026-09-01 on 2026-10-16, the entry is added to Unreleased after the 2026.10.5 release, so readers are told an upcoming release fixes an already-resolved workflow failure.
Remove the entry from Unreleased or place it under the release in which the fix was completed.
</issue_to_address>
### Comment 2
<location path="CHANGELOG.md" line_range="7" />
<code_context>
+
+### Fixed
+
+- Daily Release workflow is failing ([pm-beads-github-be8d2d927676-85](https://github.com/unbraind/pm-beads/blob/main/.agents/pm/issues/pm-beads-github-be8d2d927676-85.toon))
+
## 2026.10.5 - 2026-10-05
</code_context>
<issue_to_address>
**Closure reason omits the fix**
When the closed tracker item is used to understand why the failure was resolved, the imported record gives only `close_reason: GitHub issue #85 closed`, while its body describes the failed run rather than the resolution, so readers cannot tell what fixed the workflow.
Include the actual resolution in the imported record, or avoid claiming that the record documents it.
</issue_to_address>Sourcery assessment
Approval pending. 2 findings to address first.
Blocking findings: CHANGELOG.md:7, CHANGELOG.md:7
|
|
||
| ### Fixed | ||
|
|
||
| - Daily Release workflow is failing ([pm-beads-github-be8d2d927676-85](https://github.com/unbraind/pm-beads/blob/main/.agents/pm/issues/pm-beads-github-be8d2d927676-85.toon)) |
There was a problem hiding this comment.
🟡 Medium · Resolved issue appears upcoming
When the sync imports the GitHub issue closed on 2026-09-01 on 2026-10-16, the entry is added to Unreleased after the 2026.10.5 release, so readers are told an upcoming release fixes an already-resolved workflow failure.
Remove the entry from Unreleased or place it under the release in which the fix was completed.
Prompt for AI agents
In `CHANGELOG.md` at line 7:
**Resolved issue appears upcoming**
When the sync imports the GitHub issue closed on 2026-09-01 on 2026-10-16, the entry is added to Unreleased after the 2026.10.5 release, so readers are told an upcoming release fixes an already-resolved workflow failure.
Remove the entry from Unreleased or place it under the release in which the fix was completed.
There was a problem hiding this comment.
The root cause is in pm-github's import and is fixed in unbraind/pm-github#142. Once the caller adopts that release, its next scheduled sync will regenerate this PR.
|
|
||
| ### Fixed | ||
|
|
||
| - Daily Release workflow is failing ([pm-beads-github-be8d2d927676-85](https://github.com/unbraind/pm-beads/blob/main/.agents/pm/issues/pm-beads-github-be8d2d927676-85.toon)) |
There was a problem hiding this comment.
🟡 Medium · Closure reason omits the fix
When the closed tracker item is used to understand why the failure was resolved, the imported record gives only close_reason: GitHub issue #85 closed, while its body describes the failed run rather than the resolution, so readers cannot tell what fixed the workflow.
Include the actual resolution in the imported record, or avoid claiming that the record documents it.
Prompt for AI agents
In `CHANGELOG.md` at line 7:
**Closure reason omits the fix**
When the closed tracker item is used to understand why the failure was resolved, the imported record gives only `close_reason: GitHub issue #85 closed`, while its body describes the failed run rather than the resolution, so readers cannot tell what fixed the workflow.
Include the actual resolution in the imported record, or avoid claiming that the record documents it.There was a problem hiding this comment.
The root cause is in pm-github's import and is fixed in unbraind/pm-github#142. Once the caller adopts that release, its next scheduled sync will regenerate this PR.
dc108ab to
9f19ca0
Compare
492d59c to
b6729eb
Compare
1 participant
Automated pm-github issue synchronization for unbraind/pm-beads.
The import ran with
--gate: the plan was verified for completeness and provenance idempotency before the write, and the proposed tracker change passed the fail-closed privacy gate before anything was committed.mainis never pushed directly.Tracker items changed:
Summary by Sourcery
Track the Daily Release workflow failure through the gated GitHub issue synchronization.
Bug Fixes:
Chores: