Skip to content

Commit 2291a14

Browse files
committed
Remove build status badge from README (#3195)
## Issue Addressed Removes the build status badge from the main README.md. I don't think it actually serves a purpose and it also has the downside that a spurious failure gives us a red badge. For example, v2.2.1 failed with a [spurious failure](https://github.com/sigp/lighthouse/runs/5984392665?check_suite_focus=true) and I can't see a way to re-trigger that run. It will be red until our next release. The same test suite runs when we merge into `unstable`, so those tests must have already passed in order for the commits to get onto `stable` (assuming our workflow is followed). Github will send notifications on failed CI, so we'll still be alerted to a failure without checking this badge.
1 parent 6eaeaa5 commit 2291a14

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,8 @@
22

33
An open-source Ethereum consensus client, written in Rust and maintained by Sigma Prime.
44

5-
[![Build Status]][Build Link] [![Book Status]][Book Link] [![Chat Badge]][Chat Link]
5+
[![Book Status]][Book Link] [![Chat Badge]][Chat Link]
66

7-
[Build Status]: https://github.com/sigp/lighthouse/workflows/test-suite/badge.svg?branch=stable
8-
[Build Link]: https://github.com/sigp/lighthouse/actions
97
[Chat Badge]: https://img.shields.io/badge/chat-discord-%237289da
108
[Chat Link]: https://discord.gg/cyAszAh
119
[Book Status]:https://img.shields.io/badge/user--docs-unstable-informational

0 commit comments

Comments
 (0)