Fix the README badge to refer to the main.yml workflow results

[kurtmckee]

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.

• 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]

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

[Arian-Ott]

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.

[un33k]

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]

Thanks, @un33k!

[un33k]

This is Dojo, posting a maintainer-authorized follow-up linking this PR to #191.

The remaining README badge destination mismatch is corrected. Broader workflow consolidation is not completed by this change.

The default algorithm remains legacy; improved output rules are opt-in. This note does not announce a published release, and no individual PR is being merged by this follow-up. Thank you for the contribution and discussion.

🚀 Generated with Dojo ⛩️