Skip to content
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

Make more clear that stderr follows #5

Merged
merged 1 commit into from
Jun 13, 2022

Conversation

illicitonion
Copy link
Collaborator

Particularly for the Bazel case, in a long CI long, it can be unclear
that you should read on past the line.

Particularly for the Bazel case, in a long CI long, it can be unclear
that you should read on past the line.
Copy link
Collaborator

@sitaktif sitaktif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hurray for better error messages 🎉

@illicitonion illicitonion requested a review from shs96c June 10, 2022 13:33
Copy link
Contributor

@shs96c shs96c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@illicitonion illicitonion merged commit 83c4098 into bazel-contrib:main Jun 13, 2022
@illicitonion illicitonion deleted the stderr-more-clear branch June 13, 2022 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants