Closed distantnative closed 2 years ago
Ok this GitHub code space experiment didn't work - changes all file permissions.
@lukasbestle any idea how to clean this up to only include the actual changes?
644
for all files is actually correct and matches what we have in the kirby
repo. 755
means that the files are executable, but they shouldn't be.
I wonder why the files in the kirby
directory of this repo ended up as 755
in the first place. @bastianallgeier Do you do anything special when you update the Starterkit on each release?
@distantnative I've pushed the permission changes to main
separately to get them out of this PR so we can see the remaining changes better. Then I've rebased this PR branch. I've also needed to clean up the following:
vendor
folder and a composer.lock
. Maybe GitHub automatically ran composer install
in the root of the Starterkit?kirby/config/blueprints/site.yml
was also changed. Was this an accident or did you intend to change it? I've reverted it for now. If we want to do it, we should do it in the kirby
repo.
Since we are deprecating
headline
prop...