Skip to content

Conversation

AminTopGamer
Copy link

@AminTopGamer AminTopGamer commented Feb 16, 2025

Description

  1. I just shortened the filename and replaced it everywhere it is mentioned.
  2. To fix this error:
error: unable to create file fixtures/webstudio-features/public/assets/DALL_E_2023-10-30_12.39.46_-_Photo_logo_with_a_bold_cat_silhouette_centered_on_a_contrasting_background_designed_for_clarity_at_small_32x32_favicon_resolution_00h6cEA8u2pJRvVJv7hRe.png: Filename too long
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Steps for reproduction

/

Code Review

  • hi @kof, I need you to do
    • detailed review (read every line)

Before requesting a review

  • made a self-review
  • added inline comments where things may be not obvious (the "why", not "what")

Before merging

  • tested locally and on preview environment (preview dev login: 0000)
  • updated test cases document
  • added tests
  • if any new env variables are added, added them to .env file

Copy link

github-actions bot commented Feb 16, 2025

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

Unknown release type "Fix" found in pull request title "Fix: Too long filename error when cloning". 

Available types:
 - feat
 - fix
 - docs
 - style
 - refactor
 - perf
 - test
 - build
 - ci
 - chore
 - revert
 - experimental
Release types
  • feat - A new feature
  • fix - A bug fix
  • docs - Documentation only changes
  • style - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor - A code change that neither fixes a bug nor adds a feature
  • perf - A code change that improves performance
  • test - Adding missing tests or correcting existing tests
  • build - Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci - Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore - Other changes that don't modify src or test files
  • revert - Reverts a previous commit
  • experimental - Flagged feature

@AminTopGamer AminTopGamer changed the title Fixes too long filename error when cloning Fix: Too long filename error when cloning Feb 16, 2025
@kof
Copy link
Member

kof commented Feb 17, 2025

Unfortunately this is not how it works. This is a project that is used as a fixture, all data is synced and generated and can't be edited. File name needs to be fixed in the project first.

@istarkov
Copy link
Member

istarkov commented Mar 4, 2025

It should not be an issue when using git.
Probably bad git config i.e.

git config --system core.longpaths true

@istarkov istarkov closed this Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants