Fix the README badge to refer to the main.yml workflow results#165
Merged
Arian-Ott merged 1 commit intoun33k:masterfrom Jan 7, 2026
Merged
Fix the README badge to refer to the main.yml workflow results#165Arian-Ott merged 1 commit intoun33k:masterfrom
main.yml workflow results#165Arian-Ott merged 1 commit intoun33k:masterfrom
Conversation
Collaborator
|
LGTM. Thanks for bringing this up. |
Owner
|
All, The contributions have not gone unnoticed. I am in the middle of launching ehAye Engine and expect to push to PyPI soon. Thank you for your contributions. Thanks, |
Contributor
Author
|
Thanks, @un33k! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes the CI badge in the README, which was pointing to the CI results in the
cibranch (which are currently failing).I generally recommend against including badges in the README, as they are permanently locked when publishing to PyPI and can cause the PyPI page to look like the project is unhealthy (for example, if the badge hosting service closes shop, or if CI starts failing).
In fact, this is currently the case, and can only be fixed by publishing a new release of the package.