Improve visibility of build failures in workflows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
Community Note
Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
Feature Spec
Previously, build failures in GitHub are hidden amongst the rest of the output. This was due to Nx running things in parallel and not highlighting failures.
Now, build failures are printed last (or are at least much more visible) and added as a summary to the step itself so that you don't even really need to look at the full logs.
Use Cases
Improve developer feedback loop
Implementation Notes
No response
Component
Contributor Experience
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Nx build commands and GitHub Actions workflow steps that produce the build output. Compare how parallel failures are currently displayed with the requested behavior; done means failures are clearly visible at the end and summarized on the workflow step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100