Feature: Add Configurable GitLab Support to `ce-babysit-pr`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- gitlab, typescript
- Domain
- cli
Research direction
Start by locating the existing ce-babysit-pr workflow and its platform-specific seam, then inspect the pr-snapshot fetch/fetch_threads layer and ce-resolve-pr-feedback integration. Determine how GitHub/GitHub CLI calls are isolated and what existing abstractions could support glab before implementing Phase 1. Done means GitLab repositories can fetch MR discussions and resolution state, with actionable feedback handled consistently, while CI/CD and branch/merge support remain outside the initial scope.
Written by the indexing model from the issue text.
Description
Problem
/ce-babysit-pr is currently GitHub-only and exits when the repository remote is GitLab.
This makes the skill unavailable for teams using GitLab merge requests, even though the core workflow appears applicable to GitLab as well.
The current documentation also mentions that GitLab support is mappable in principle using glab, merge requests, discussions, pipelines, and detailed_merge_status.
Proposed Approach
Add GitLab support incrementally while keeping platform-specific logic isolated behind the existing platform seam.
Rather than implementing the complete GitLab workflow in a single change, the work could be split into smaller MRs.
Phase 1: Review Feedback
The first implementation would focus on the review feedback workflow:
- Detect GitLab repositories and use
glab - Add GitLab implementations for the
pr-snapshotfetch/fetch_threadslayer - Support GitLab MR discussions and resolution state in
ce-resolve-pr-feedback - Allow
/ce-babysit-prto watch for and handle actionable review feedback on GitLab MRs
This would provide the core workflow:
Watch MR
↓
New actionable review feedback
↓
Delegate to ce-resolve-pr-feedback
↓
Apply fix / reply / resolve discussion
↓
Continue watching
Phase 2: CI/CD and Pipeline Handling
A follow-up MR could add GitLab pipeline support, including:
- Mapping GitLab pipeline and job status to the CI state consumed by
ce-babysit-pr - Handling pipeline failures
- Retrying transient failures where appropriate
- Delegating genuine failures to
ce-debug
Phase 3: Branch and Merge State
Further support could include:
- Detecting when the target branch has moved
- Mapping GitLab mergeability and MR state, such as
detailed_merge_status - Integrating branch maintenance into the babysitting workflow
Configurable Workflow
Ideally, the different parts of the babysitting workflow should be independently configurable.
For example, users could choose to babysit:
- Review comments only
- CI/CD only
- Branch/merge state only
- Any combination of the above
- The complete workflow
This would allow users to enable only the behavior they need. For example, someone who only wants automatic handling of incoming review comments would not need to enable CI/CD monitoring, while another user could use the skill primarily to monitor and handle pipeline failures.
The higher-level babysitting loop could remain platform-agnostic where possible, with GitHub and GitLab implementations providing the required platform-specific state and actions.
Potential Platform Equivalents
| GitHub | GitLab |
|---|---|
| Pull Request | Merge Request |
gh |
glab |
| Review threads | MR discussions / resolvable threads |
| GitHub Actions | Pipelines |
| PR merge state | detailed_merge_status / MR state |
Questions
Before starting implementation, I would like to understand whether GitLab support is something the project would want to accept and whether this incremental approach aligns with the intended architecture.
In particular:
- Does splitting the implementation into separate MRs for review feedback, CI/CD, and branch/merge state make sense?
- Should these babysitting capabilities be independently configurable, allowing users to enable only comments, only CI/CD, or any combination?
- Is the proposed platform abstraction direction aligned with the project?
- Is there an existing abstraction or architectural direction planned for supporting multiple git hosting providers?
I am interested in working on this if the maintainers are open to the approach. I may not be able to start immediately, but if nobody else picks it up, I would be happy to start working on the initial review feedback support in the coming weeks.
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 80/100
EveryInc/compound-engineering-plugin#2084 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2083 ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
hurttlocker/o8#6535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
snapotter-hq/SnapOtter#4856 ·
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day