Skip to content

Conversation

eike-hass
Copy link
Collaborator

@eike-hass eike-hass commented Aug 27, 2025

Description of change

set git longpaths config to allow path > 260 chars

Links to any relevant issues

Fixes issues like this

Type of change

Add an x to the boxes that are relevant to your changes.

  • Bug fix (a non-breaking change which fixes an issue)
  • Enhancement (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Fix

How the change has been tested

CI passes

Change checklist

Add an x to the boxes that are relevant to your changes.

  • I have followed the contribution guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@eike-hass eike-hass added the No changelog Excludes PR from becoming part of any changelog label Aug 28, 2025
@eike-hass eike-hass requested a review from a team August 28, 2025 08:25
@wulfraem
Copy link
Contributor

The description should be

set git longpaths config to allow path > 260 chars

right? :D

@eike-hass
Copy link
Collaborator Author

The description should be

set git longpaths config to allow path > 260 chars

right? :D

OFC 🙈

@eike-hass eike-hass merged commit 3d5c925 into main Aug 29, 2025
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
No changelog Excludes PR from becoming part of any changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants