I maintain an open source project and noticed that the CircleCI badge has changed from being a simple indicator, to also notifying people of CircleCI 1.0 being sunsetted.
Frankly, I’m not happy about this. This indicator seems to imply to users that there is something wrong with the project, even though the project has always been using CircleCI v2.
I do not want my users to have to see this for the next 2.5 months. It is information that is entirely irrelevant to the usage of the project.
Edit: As pointed out in the below comments, the wording of the indicator is also problematic since it is not clear that it’s CircleCI, and not the project, which is sunsetting its 1.0 branch.
I would like a way to clear this indicator from projects that have been verified as using CircleCI v2.
Perhaps this could take the form of an extra parameter on the badge URL:
Using that endpoint would give you the simple build indicator, and not include additional notifications about CircleCI’s 1.0 sunsetting.
Alternatively, CircleCI could change the badge returned based on the version used in the latest build(s). For projects using 2.0, return the badge without the sunsetting indicator.
This solution keeps it DRY, as project maintainers wouldn’t have to keep the badge URL in sync with the actual config file.