Problem/Motivation
While setting up the Governor theme to be used as a starterkit, the command is throwing an error:
[ERROR] Paths were defined "no_edit" but no files found.
Steps to reproduce
1. Clone “The Governor” theme in the “web/themes/custom/” folder. (This step will be replaced by composer require in the future.)
2. Run the generate-theme command from the root the project:
php web/core/scripts/drupal generate-theme my_new_theme --name "My New Theme" --description "Custom theme generated from The Governor" --path "themes/custom" --starterkit=governor
Comments
Comment #3
nikitaaswani commentedComment #4
shamir.vs commentedThank you, @nikitaaswani, for the work. I have applied the patch, and the issue has been resolved. Attaching screenshots of the before and after results.
Before applying the patch

After applying the patch
Comment #5
spicy.werewolf commentedNice! One thing I'd like to do is to follow core starterkit and leave the keys in the starterkit.yml file:
While strictly speaking this issue is to resolve the missing file error, and the generate script seems to run with no overt errors, there are a couple of issues with the generated
MY_NEW_THEME.info.ymlfile that surface in code testing that I want to document here. There is currently an open issue for PHPCS errors that are surfacing after the generate script is run: https://www.drupal.org/project/governor/issues/3401702however these issues are starting to overlap each other.
Adding a placeholder description is easy enough to do. We can just add it to the "info" in
governor.starterkit.ymlSomething like:For the "version" warning, it appears we may need to some additional configuration to remove the line from the info file.
Comment #6
spicy.werewolf commentedUpdate: the "Version" warning appears to be a core bug. See: https://www.drupal.org/project/governor/issues/3401702#comment-16359121
Comment #7
spicy.werewolf commented