release:tag: a rerun after a rejected tag push stops on the local action-v tag
維護者通常 1 天內回覆
評估
- 難度
- 1/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 20/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 停滯
- 技術堆疊
- git, node.js, typescript
研究方向
Read scripts/release-tags.mjs and inspect how it creates the annotated action-v<version> tag compared with the other two tags. The issue gives a reproduction using version 9.9.9; check the script's behavior after those local tags exist. Done means rerunning the command can push all three tags after a rejected push, while the existing remote tag checks remain in place. An open linked pull request (#280) indicates work is already underway.
由索引模型根據 Issue 內容生成。
描述
npm run release:tag (scripts/release-tags.mjs) creates the three release tags locally, then pushes them in one atomic push. When that push is rejected (network error, a protected-tag rule, a missing permission), the tags it created stay in the local clone. Running the command again then stops before pushing anything:
fatal: tag 'action-v9.9.9' already exists
The v<version> and cli-release-v<version> tags are created with git tag -f, so they are replaced on a rerun. The annotated action-v<version> tag is created with git tag -a and no -f, so it is not. The only way out is to delete the local tag by hand, even though the script's header says reruns are expected ("The workflow accepts tags that already exist").
Reproduce
- In a clone whose
originhas the release commit onmainand no release tags, create the local tags a rejected push leaves behind:git tag v9.9.9,git tag -a action-v9.9.9 -m xandgit tag cli-release-v9.9.9, withpackages/diffci-cli/package.jsonat version9.9.9. - Run
node scripts/release-tags.mjs.
Expected: the three tags are pushed at HEAD. Actual: fatal: tag 'action-v9.9.9' already exists, and nothing is pushed.
The tags on origin are still checked before anything is created, so passing -f to the annotated tag only replaces a local tag that was never published.
- 主要語言
- TypeScript
- 星號
- 0
- 分支
- 4
- 平均合併
- 18 小時 41 分鐘
- 30 天內合併 PR
- 48
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
DiffCI/core 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at random可能已有人在做 @FredApps 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆
-
Agent tools: changed_files lists only the new path of a renamed file可能已有人在做 @FredApps 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
adapter good first issue
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
相似的 Issue
-
agent-ready area: ui-server priority: p3 type: test
難度 2/5 1-3 小時 新手友好度 78/100
schlessera/brain-kit#4249 ·
維護者通常 1 天內回覆
-
documentation tool triaged
難度 2/5 1-3 小時 新手友好度 73/100
can1357/oh-my-pi#19608 · 2 則留言 ·
維護者通常 1 天內回覆
-
dependencies tech-debt
難度 2/5 1-3 小時 新手友好度 65/100
bcgov/nr-waste-plus#1549 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
blixvip/solana-tx-parse#18 ·