Skip to content

fix: warning should not result in non-zero exit code#1872

Merged
snitin315 merged 5 commits intonextfrom
fix/exit-codes
Oct 5, 2020
Merged

fix: warning should not result in non-zero exit code#1872
snitin315 merged 5 commits intonextfrom
fix/exit-codes

Conversation

@snitin315
Copy link
Copy Markdown
Member

@snitin315 snitin315 commented Oct 5, 2020

What kind of change does this PR introduce?
fix

Did you add tests for your changes?
Yes
If relevant, did you update the documentation?
Yes
Summary
A warning should not result in a non-zero exit code as it's not braking build or something else.
Refers #1836 (comment)

Does this PR introduce a breaking change?
No

Other information
Fixes #1836

@snitin315 snitin315 requested a review from a team as a code owner October 5, 2020 05:05
@alexander-akait
Copy link
Copy Markdown
Member

/cc @webpack/cli-team

@webpack-bot
Copy link
Copy Markdown

@snitin315 Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@Dheeraj-01 Please review the new changes.

@snitin315 snitin315 merged commit ae9539d into next Oct 5, 2020
@snitin315 snitin315 deleted the fix/exit-codes branch October 5, 2020 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Performance.hints: "warning" emits non zero exit code

6 participants