Microsoft/vscode

GitHub - improving git error message for fatal error in commit_refs

Open

#182,679 建立於 2023年5月16日

在 GitHub 查看
 (0 留言) (1 反應) (1 負責人)TypeScript (74,848 star) (10,221 fork)batch import
buggithelp wantedpapercut :drop_of_blood:

描述

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.78.2
  • OS Version: Ubuntu 23.04

Steps to Reproduce:

  1. Run git push
  2. An error message is shown "Can't push refs to remote. Try running "Pull" first to integrate your changes"
  3. Click on "Show Command output"
> git push -u origin output
remote: Resolving deltas:   0% (0/3)        
remote: Resolving deltas:  33% (1/3)        
remote: Resolving deltas:  66% (2/3)        
remote: Resolving deltas: 100% (3/3)        
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.        
remote: fatal error in commit_refs        
To github.com:user/repo.git
 ! [remote rejected]           output -> output (failure)
error: failed to push some refs to 'github.com:user/repo.git'

A quick google search reveals that "fatal error in commit_refs" means that GitHub is currently not working.

Current error message

Can't push refs to remote. Try running "Pull" first to integrate your changes

Improved error message

Can't push refs to remote. This is probably a GitHub issue. Check https://www.githubstatus.com/ for details.

貢獻者指南

技術棧
typescriptnodejs
領域
developer experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScriptVS Code extension development
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Search the VS Code codebase for the error message string 'Can't push refs to remote. Try running "Pull" first to integrate your changes'. It is likely in a git extension file, possibly in a locale/messages file. After locating the string, replace it with a message that suggests checking GitHub status, such as 'Can't push refs to remote. This is probably a GitHub issue. Check https://www.githubstatus.com/ for details.'. Ensure the change is consistent with the project's localization approach. Note that the issue already has an assignee, so coordinate with the maintainer before starting.