oh-my-pr 2.4.0 → 2.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +12 -21
  2. package/dist/index.cjs +175 -72
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
- # Code Factory
1
+ # Oh-my-PR
2
2
 
3
- **Local-first GitHub PR babysitter for Codex and Claude.**
3
+ **Local-first GitHub PR babysitter for Codex and Claude**
4
4
 
5
5
  <p align="center">
6
6
  <img width="409" height="409" alt="Code Factory logo" src="https://github.com/user-attachments/assets/ca339a71-40d9-4619-900f-55825f30a57f" />
@@ -12,9 +12,7 @@
12
12
  [![Node.js 22+](https://img.shields.io/badge/Node.js-22%2B-green.svg)](https://nodejs.org/)
13
13
  [![TypeScript](https://img.shields.io/badge/TypeScript-strict-blue.svg)](https://www.typescriptlang.org/)
14
14
 
15
- Code Factory watches GitHub repositories, syncs PR feedback, triages what matters, and dispatches locally installed coding agents inside isolated app-owned worktrees. It keeps durable state in `~/.oh-my-pr` and exposes the same system through a dashboard, REST API, and MCP server.
16
-
17
- No hosted service. No agent edits inside your working copy. Your PR automation stays on your machine.
15
+ Oh-my-pr babysits your PRs from your local machine, reads all PR comments and CI/CD logs, and gets your PR ready for merge to main. It uses your local Claude Code or Codex to address any issues identified in the PR or CI/CD pipeline and to ensure that any documentation is up to date. You can push a PR, walk away, and come back to a clean PR ready to be merged.
18
16
 
19
17
  <img width="1365" height="686" alt="Code Factory dashboard" src="https://github.com/user-attachments/assets/66dfa082-c732-4989-8b05-f19aa550acb5" />
20
18
 
@@ -22,26 +20,19 @@ No hosted service. No agent edits inside your working copy. Your PR automation s
22
20
 
23
21
  - Watch multiple repositories or add a single PR by URL.
24
22
  - Auto-register open PRs, archive closed or merged PRs, and keep syncing review activity.
25
- - Pause background automation for an individual tracked PR while keeping manual runs available.
26
- - Store PR state, questions, logs, and social changelogs in SQLite with mirrored log files.
27
- - Triage feedback into `accept`, `reject`, or `flag`, with manual overrides and retry for failed or warned items.
28
- - Run `codex` or `claude` in isolated worktrees under `~/.oh-my-pr`, then push verified fixes back to the PR branch.
29
- - Evaluate review comments and failing CI statuses, post GitHub follow-ups, resolve review threads, and persist CI healing sessions per PR head.
30
- - Detect merge conflicts and optionally let the agent resolve them automatically.
23
+ - Evaluate review comments and failing CI statuses, post GitHub follow-ups, resolve review threads, and heal any CI failures.
24
+ - Detect merge conflicts and let the agent resolve them automatically.
31
25
  - Ask natural-language questions about any tracked PR from the dashboard or via MCP.
32
- - Configure trusted reviewers, ignored bots, polling, batching, run limits, and CI-healing retry budgets from settings.
33
- - Enable drain mode to pause new work and wait for active runs to finish before deploys or upgrades.
34
- - Check onboarding status, install Claude or Codex review workflows, and generate social changelogs every 5 PRs merged to `main`.
35
- - Use the React dashboard, local REST API, MCP server, or optional Tauri desktop shell.
36
26
 
37
27
  ## How It Works
38
28
 
39
- <img width="969" height="572" alt="Code Factory workflow" src="https://github.com/user-attachments/assets/b9dbd102-ae2e-4837-a862-a0282bdfa0b8" />
40
-
41
29
  1. Add a repository to the watch list or register a PR directly by URL.
42
- 2. The watcher polls GitHub, auto-registers open PRs, syncs reviews and comments, archives PRs that closed upstream, records failing CI on the current head SHA, and queues babysitter runs for tracked PRs whose background watch is enabled.
43
- 3. Accepted work is executed in an app-owned repo cache and isolated git worktree under `~/.oh-my-pr`.
44
- 4. The agent applies fixes, verifies the result, pushes to the PR branch, updates GitHub threads, and writes logs for the full run.
30
+ 2. The watcher enqueues a durable repo-sync job in SQLite.
31
+ 3. That sync job polls GitHub, auto-registers open PRs, syncs reviews and comments, archives PRs that closed upstream, records failing CI on the current head SHA, and queues babysitter runs for tracked PRs whose background watch is enabled.
32
+ 4. Manual apply/babysit requests, PR questions, release processing, and social changelog generation go through the same durable queue before work executes in an app-owned repo cache and isolated git worktree under `~/.oh-my-pr`.
33
+ 5. The agent applies fixes, verifies the result, pushes to the PR branch, updates GitHub threads, and writes logs for the full run.
34
+
35
+ Repo sync, babysit/apply, PR Q&A, release processing, and social changelog generation all run through durable background jobs stored in `state.sqlite`. On startup the dispatcher reclaims expired job leases, and interrupted babysitter runs are resumed from stored run context when possible.
45
36
 
46
37
  ## CI Healing
47
38
 
@@ -120,7 +111,7 @@ Use it with MCP hosts such as Claude Desktop or OpenClaw, or call the REST API d
120
111
 
121
112
  By default Code Factory stores its runtime data in `~/.oh-my-pr`:
122
113
 
123
- - `state.sqlite` for durable app state
114
+ - `state.sqlite` for durable app state, runtime flags, background jobs, questions, releases, and changelogs
124
115
  - `log/` for mirrored activity logs
125
116
  - `repos/` for app-owned repository caches
126
117
  - `worktrees/` for isolated PR worktrees