-
-
Notifications
You must be signed in to change notification settings - Fork 9
Disable initialize_documentation for subtemplates #218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ef04e51
to
d49940f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor tweaks for consistency and clarity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked out this branch, tested locally, works great!
Completely overlooked this way of implementation. Works great + super clean! LGTM. |
I don't know why CI doesn't report its status here. It's all green at https://github.com/plone/cookieplone-templates/actions/runs/14487515096. I'll hold off on merging, just in case I'm mistaken, and to let @davisagli or @ericof take a look at it. |
@stevepiercy I also don't understand why CI was not triggered. Your new commit should have triggered a pull_request.synchronize event, which should have started the workflow. I'll make another commit just to bump it, but let's watch other PRs to see if it's a broader issue vs a GitHub glitch. |
This is my proposal instead of #204. Set the
enabled
flag for the subtemplate based on theinitialize_documentation
variable, and set that variable to 0 when calling the frontend and backend addon templates as subtemplates./cc @ujsquared