You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We often realize belatedly that merged PRs contain lint warnings re: potential exceptions, increasing the risk for crashes in production versions after the PRs are merged in. It would be too big a burden to ask our reviewers to manually check the code they are merging for any lint warnings.
Anyone know if we can integrate this check into our Travis or Codacy CIs?
The text was updated successfully, but these errors were encountered:
We often realize belatedly that merged PRs contain lint warnings re: potential exceptions, increasing the risk for crashes in production versions after the PRs are merged in. It would be too big a burden to ask our reviewers to manually check the code they are merging for any lint warnings.
Anyone know if we can integrate this check into our Travis or Codacy CIs?
The text was updated successfully, but these errors were encountered: