Do not print build commands for every element being built
Open
enhancement
logging
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
For one, just 20 lines is not enough to fit most build instructions in my experience. For two, I do not think it adds any value, am I missing a use case? This information is logged per element already. There is already machinery to print logs when an element fails to build, which is actually useful.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Trace where per-element build commands are printed and compare that path with the existing failure-log handling; done means routine builds no longer print those commands while failed builds still expose their useful logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100