Merged
Conversation
dinosath
approved these changes
Mar 1, 2026
Instead of capturing stdout into a buffer and printing it after the hook finishes, inherit stdout directly when post_hook_print_stdout is true. This ensures hook output (e.g. progress messages before uv sync) appears in the correct order relative to subprocess stderr output.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Post-hook scripts often print important next steps (for example, setup commands or onboarding notes).
Today that output is mostly hidden in debug logs, so users can complete generation but still miss required actions.
Intent
Make post-generation guidance visible only when template authors explicitly want it.
Constraints
Risk
If enabled, anything printed by the hook becomes visible in terminal/CI logs, so templates should avoid printing secrets.