Skip to content

Conversation

@coolharsh55
Copy link
Contributor

Since there is no way to restrict slack notifications from forked builds, I vote to remove the slack notification to reduce spam. Refers to #22

@codecov-io
Copy link

Current coverage is 0.00%

Merging #23 into master will not affect coverage as of eda5331

No diff could be generated. No reports for #23 found.
Review entire Coverage Diff as of eda5331

Powered by Codecov. Updated on successful CI builds.

@SanketDG
Copy link
Member

I am against this until #4722 fails to offer a solution.

@coolharsh55
Copy link
Contributor Author

I have no idea why coverage fails to report the correct coverage. Travis build 56.1 and 56.2 both report 77% coverage

The slack notifications being hard-coded in travis resulted in every forked build on travis also sending the notifications to the slack channel. Since there is no way to limit notifications to master repo, the notifications should be removed altogether.

Note: The build status is visible on every PR request, so PR can still be checked for build errors

Resolves #22

Signed-off-by: Harshvardhan Pandit <[email protected]>
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.

4 participants