如何修复“绒毛阶段”因GIT错误而失败。

发布于 2025-02-13 07:30:22 字数 344 浏览 0 评论 0原文

由于某种原因,绒毛阶段持续失败,显示出绒毛段,这是由于git错误

使用版本v13.0.3。

  ✖ lint-staged failed due to a git error.
 Cleaning up temporary files...
  Any lost modifications can be restored from a git stash:

    > git stash list
    stash@{0}: automatic lint-staged backup
    > git stash apply --index stash@{0}

For some reason, lint-staged keeps failing, showing the lint-staged due to a git error.

Using version v13.0.3.

  ✖ lint-staged failed due to a git error.
 Cleaning up temporary files...
  Any lost modifications can be restored from a git stash:

    > git stash list
    stash@{0}: automatic lint-staged backup
    > git stash apply --index stash@{0}

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

魂归处 2025-02-20 07:30:22

我遇到了一个类似的问题,事实证明这是由文件权限引起的。我能够通过修复权限来解决问题。

我使用以下脚本将其更改为所有文件。

sudo chown -R $(whoami) <path_to_repo>

执行此命令后,解决了问题。

I encountered a similar problem, which turned out to be caused by file permissions. I was able to resolve the issue by by fixing the permissions.

I used the below script to change it for all files.

sudo chown -R $(whoami) <path_to_repo>

After executing this command, the issue was resolved.

独行侠 2025-02-20 07:30:22

解决了这个问题。我检查了我的.git文件夹,并找到了lint-staged_unstaged.patch file。我删除了这一点并解决了问题。

Solved this issue. I checked my .git folder and found a lint-staged_unstaged.patch file. I deleted that and resolved the issue.

柒七 2025-02-20 07:30:22

首先,您需要检查git日志文件,并查看它避开您的消息,例如,这是我的git日志:

⧗输入:壮举:: sparkles :( 这是我的提交消息

在这里,是我的提交消息的较长描述)✖标题
必须不超过100个字符,当前长度为102
[标头 - 最大长度]

✖发现了1个问题,0警告ⓘ获得帮助:
https://github.com/github.com/conventional-commitlink/commitlint/commitlint/commitlint/commitlint/what----- IS-Commitlint

沙哑的 - commit -msg挂钩,用代码1(错误)

退出

挂钩看到问题是关于标题(提交消息)超过100个字符的标头式长度,因此您应该使其更短。

first you need to check the git log file, and see the message it gaves you, for example, this was my git logs :

⧗ input: feat: :sparkles: (here, is my commit message)

(here, is the longer description of my commit message) ✖ header
must not be longer than 100 characters, current length is 102
[header-max-length]

✖ found 1 problems, 0 warnings ⓘ Get help:
https://github.com/conventional-changelog/commitlint/#what-is-commitlint

husky - commit-msg hook exited with code 1 (error)

as you can see the problem is about the header (commit message) exceeding the header-max-length of 100 characters, so you should make it shorter.

心不设防 2025-02-20 07:30:22

运行以下命令解决的问题:

yarn lint (eslint --fix "src/**/*.{js,jsx,ts,tsx}" & yarn format)

my problem fixed by run the following command:

yarn lint (eslint --fix "src/**/*.{js,jsx,ts,tsx}" & yarn format)
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文