Start flow steps with a divergence check against origin/main
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, github, typescript
- Domain
- developer-experience
Research direction
The flow-reminders hook and the workflow doc are the two places to change; find where the hook injects reminders for /implement, /implement-spec and /pr, and where each step's guard rails are written. Add the git fetch and git log HEAD..origin/main check to all three steps, and make a step that finds new commits report them and ask before merging. Done when the hook's tests cover the new reminder and the workflow doc names the check in each step.
Written by the indexing model from the issue text.
Description
What to build
/implement, /implement-spec and /pr begin with git fetch and git log HEAD..origin/main, and report any new commits before continuing. The check runs through the flow-reminders hook and a step in the workflow doc, so it does not depend on an agent remembering.
Origin: the retro of PR #134. main moved mid-session (an oxc and Biome fix) and the maintainer had to tell the agent to pull it in.
Acceptance criteria
- The hook injects the divergence check for the three flow steps.
- The workflow doc names the check in each step's guard rail.
- A step that finds new commits on
mainreports them and asks before merging them in. - The hook's tests cover the new reminder.
Blocked by
None (can start immediately).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 64
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 nemchik/biome-plugin-suitescript
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
nemchik/biome-plugin-suitescript#137 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nemchik/biome-plugin-suitescript#87 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nemchik/biome-plugin-suitescript#48 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nemchik/biome-plugin-suitescript#136 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 35/100
nemchik/biome-plugin-suitescript#135 ·
Maintainers usually reply within 1 day
All issues in nemchik/biome-plugin-suitescript
Similar issues
-
parse: child keys like `007`, `1e3`, `0x1f`, `-1` make the parent an empty array and hide the valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
bketelsen/pi-pocket-team#232 ·
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
area: interop area: sip-core v3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fonoster/routr#705 · 1 comment ·
Maintainers usually reply within 1 day