docs(readme): apply Codex P2 feedback on #19 - #20
Merged
Merged
Conversation
Two P2 issues from chatgpt-codex-connector on PR #19: 1. Lower download buttons (lines 85, 88) still pointed to v1.0.0. Update to v1.0.1 so all release-specific download links match. 2. CI status badge filtered by branch=master, but build-and-release.yml triggers on tag pushes only (v*). The branch filter would always show "no status". Switch the badge to event=push so it tracks the actual release workflow runs; rename label "CI" β "Release" to match what it represents. No new release tag β README asset URLs are now aligned with v1.0.1.
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.
What
Two surgical README fixes per chatgpt-codex-connector review on PR #19:
branch=masterbutbuild-and-release.ymlonly runs onv*tag pushes β badge would always show "no status"event=push(tracks tag pushes) and relabeled CI β ReleaseWhy
Both are real bugs: lower buttons currently send users the previous release, and the CI badge is misleading.
Verify
shields.io URLs resolve. No tag/rebuild needed (README only).