CI push runs on feature branches fail at the grammar-data range check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
Research direction
Find the workflow step named "Check grammar-data range, checkout tip and worktree" and inspect its switch ($env:GITHUB_EVENT_NAME) push case alongside the pull_request case. Reproduce the failure with a push event where before is zero or unavailable, then check how the workflow obtains the base revision. Done means push runs on new and force-pushed branches pass the range check while preserving the PR run behavior.
Written by the indexing model from the issue text.
Description
CI's push trigger on any non-main branch fails in seconds on all three OSes. The step "Check grammar-data range, checkout tip and worktree" fails with grammar-data-hygiene: Git rev-parse failed: fatal: Needed a single revision. The pull_request run for the same commit gets past this step. Each push to a PR branch therefore adds three red jobs that mean nothing, and they appear beside the real PR checks.
Seen on app/proposal-apply: run 44514528509 (push, cb412e500) and the push run for 23223ab25. Both failed in all three build-and-test jobs at this step, while their pull_request runs ran the full suite. The step's switch ($env:GITHUB_EVENT_NAME) handles pull_request. The push branch seems to rev-parse a base that doesn't exist in a shallow checkout of a new or force-pushed branch (before = 0000… or an unfetched SHA).
Next: in the push case, fetch before or fall back to the merge-base with origin/main. Alternatively, run CI on push only for main and let PR branches rely on pull_request.
🤖 Generated with Claude Code
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- Avg merge
- 4h 4m
- Merged PRs (30d)
- 69
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 sillsdev/motif
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sillsdev/motif#304 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
Similar issues
-
area: opcua type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
RicoSuter/Namotion.Interceptor#1020 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
protocolbuffers/protobuf#31768 ·
Maintainers usually reply within 1 day
-
area: mixer area: remote bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
BrighterCommand/Brighter#4764 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
OrchardCMS/OrchardCore#20299 ·
Maintainers usually reply within 1 day