Skip to content

Conversation

@kurtmckee
Copy link
Contributor

This fixes the CI badge in the README, which was pointing to the CI results in the ci branch (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.

image
  • If the badges should be removed, let me know.
  • Separately, if the triplicated GitHub workflows should be unified down to just one YAML file, let me know.

@coveralls
Copy link

Coverage Status

coverage: 97.44%. remained the same
when pulling 4faa5f9 on kurtmckee:fix-readme-badge
into 8b0ac21 on un33k:master.

@Arian-Ott
Copy link
Collaborator

LGTM.

Thanks for bringing this up.
The last release was 2024, so it would be time for a new release as that would introduce many bug fixes and changes over the last two years.

@Arian-Ott Arian-Ott merged commit 7b6d5d9 into un33k:master Jan 7, 2026
2 checks passed
@un33k
Copy link
Owner

un33k commented Jan 7, 2026

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,
Val

https://ehaye.io

@kurtmckee kurtmckee deleted the fix-readme-badge branch January 7, 2026 17:04
@kurtmckee
Copy link
Contributor Author

Thanks, @un33k!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants