Make the README hero easier to scan at a glance#396
Closed
Conversation
added 4 commits
April 23, 2026 19:53
The top of the README buried the CLI version inside one long flat badge strip, so the hero now leads with the product name and two balanced for-the-badge rows that keep the live release, traction, and support signals readable on GitHub. A focused metadata regression now locks those hero cues in place. Constraint: GitHub README markup must stay static and render without custom CSS Rejected: Custom screenshot or banner image | would drift from live version, downloads, CI, and scorecard data Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep the hero limited to high-signal operator facts; do not collapse it back into one crowded row without updating the metadata test Tested: node --test test/metadata.test.js Tested: openspec validate --specs Not-tested: Rendered GitHub web preview
The code change is already verified and the PR is open, but the finish flow could not reach MERGED because GitHub still requires review and has all required checks queued. Recording that state in the T1 notes keeps the branch handoff truthful instead of implying cleanup completed. Constraint: Finish state must reflect GitHub merge truth, not local intent Rejected: Pretend cleanup completed | would misstate the PR lifecycle Confidence: high Scope-risk: narrow Reversibility: clean Directive: Remove this blocker note only after PR #396 is actually merged and sandbox cleanup is proven Tested: gh pr view 396 --json mergeStateStatus,reviewDecision,statusCheckRollup,url Not-tested: eventual CI results or post-merge cleanup
The README lane is still waiting on GitHub gates, but now the blockers are clearer: the configured non-author code owner cannot be resolved as a reviewer, visible collaborators only expose the PR author, and repository auto-merge is disabled. Capturing that evidence on-branch keeps the handoff actionable instead of vague. Constraint: Finish truth must include current GitHub gate failures Rejected: Leave the older blocker note as-is | it omitted the failed reviewer and auto-merge probes Confidence: high Scope-risk: narrow Reversibility: clean Directive: Replace this blocker note only after a real non-author approval exists or repo policy changes Tested: gh pr edit 396 --add-reviewer recodeecom Tested: gh pr merge 396 --auto --squash Tested: gh pr view 396 --json mergeStateStatus,reviewDecision,statusCheckRollup,url Not-tested: admin-bypass merge paths
The README lane is not only blocked by review policy; GitHub Actions are also broadly stalled for this repository. Capturing the repo-wide queue pattern and the live GitHub status incident keeps the handoff tied to external evidence instead of treating the pending checks as branch-local flakiness. Constraint: finish notes must separate repo policy blockers from external infrastructure blockers Rejected: Assume the queue is branch-specific | repo-wide queued runs and GitHub status contradict that Confidence: high Scope-risk: narrow Reversibility: clean Directive: Remove this incident note only after Actions runs actually leave queued state or the status incident resolves Tested: gh api repos/recodeee/gitguardex/actions/permissions Tested: gh run list --limit 20 --json workflowName,status,conclusion,headBranch,createdAt,updatedAt,url Tested: https://www.githubstatus.com/api/v2/incidents/unresolved.json Not-tested: eventual post-incident rerun and merge cleanup
Collaborator
Author
|
Blocked finish status as of 2026-04-23 18:03 UTC:
Unblock path once GitHub recovers: get a valid non-author code-owner approval on this PR, let the required checks actually leave |
NagyVikt
deleted the
agent/codex/readme-cli-version-and-scanability-2026-04-23-18-38
branch
NagyVikt
restored the
agent/codex/readme-cli-version-and-scanability-2026-04-23-18-38
branch
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
1 participant
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.
Automated by gx branch finish (PR flow).