Re-pull release is refused as tag-missing: GitHub rejects commits/tags/<tag>
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
Research direction
Start at the re-pull release step that reads a tag’s commit and trace how it constructs the GitHub API request; the issue does not name the source file or test. Compare the tag lookup path with the working API forms described here, then run the relevant re-pull tests against a response that matches GitHub’s 422 behavior. Done when a merged re-pull with an existing tag no longer reports tag-missing.
Written by the indexing model from the issue text.
Description
The release step of a re-pull reads the tag's commit at /commits/tags/<tag> with Accept: application/vnd.github.sha. The real GitHub API answers 422 (No commit found for SHA: tags/v2.0.0) to that spelling; /commits/refs/tags/<tag> and /commits/<tag> both answer the commit. So nemar admin repull resume refuses every merged re-pull with tag-missing, although the tag exists and points at the merge commit. Seen on on003645 (record 2) and on004362 (record 3) on 2026-11-08, both stuck at merged. The re-pull stand-ins accepted the short form, so the suites passed. Blocks enabling AUTO_REPULL_ENABLED and AUTO_REPULL_MERGE_ENABLED, because an automatic merge would mint a DOI and then fail to release.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 6h 52m
- Merged PRs (30d)
- 224
Getting set up
- No Dockerfile or Docker Compose file
- No 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 nemarOrg/nemar-cli
-
backend enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug P3
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
All issues in nemarOrg/nemar-cli
Similar issues
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
anomalyco/opencode#62873 · 1 comment ·
Maintainers usually reply within 1 day
-
code-quality good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenRailAssociation/netzgrafik-editor-frontend#1481 ·
Maintainers usually reply within 1 day
-
🙌 icon request
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
lucide-icons/lucide#5183 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 81/100
cloudflare/capnweb#293 ·
Maintainers usually reply within 2 days
-
bug implicit-state
Difficulty 2/5 1-3 hours Newbie friendliness 74/100