Repository navigation
Link libtmux.org and the package registry from the READMEs - #794
Merged
Merged
Conversation
why: The README badge row links the current docs and PyPI but not the libtmux.org home for the port, and the install heading calls a release "Stable". what: - Add a libtmux.org badge to the badge row - Label the install block "Release:" instead of "Stable release:"
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #794 +/- ##
==========================================
+ Coverage 52.37% 52.45% +0.08%
==========================================
Files 26 26
Lines 3729 3729
Branches 747 747
==========================================
+ Hits 1953 1956 +3
+ Misses 1472 1469 -3
Partials 304 304 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
why: The header row did not follow the shared libtmux badge order, and carried a second workflow badge and a coverage badge that the standard leaves out of the header. what: - Order the badges as tests, libtmux (PyPI version), libtmux.org docs, license - Point the tests badge at the tests.yml workflow page - Label the PyPI badge with the package name - Drop the docs workflow badge and the codecov badge - Use a static MIT license badge
Member
Author
|
Badge row is now CI, version, docs and license, the same four the other libtmux ports show (0813d07): tests, This drops two badges from the header:
Say if either should stay and I'll put it back. |
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.
Each README that introduces a package now links the port's docs home on libtmux.org and that package's page on PyPI, as badges under the title. The libtmux.org badge is on its own line in every README so it can become a plain link if preferred.
Release wording also drops "stable": nothing in libtmux is stable, and libtmux.org no longer publishes a stable docs version, so a release's docs live at its own version, which is the default.
docs(README) Link the README to libtmux.orgChecks: every new URL returns 200 (libtmux.org port homes 302), the README checks pass, and
git diff origin/master -- '*README.md' | grep '^-'shows no removed README lines apart from deliberate rewording.Tool use: a Sonnet sub-agent made the README commits; Claude Code reviewed them, wrote the docs workflow change where there is one, and opened this pull request. The maintainer reviews it before merge.