Skip to content

README and PR comment: clearer, standard wording#175

Merged
reuvenharrison merged 3 commits into
mainfrom
content/readme-api-change-review
Jun 23, 2026
Merged

README and PR comment: clearer, standard wording#175
reuvenharrison merged 3 commits into
mainfrom
content/readme-api-change-review

Conversation

@reuvenharrison

@reuvenharrison reuvenharrison commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Clarifies the wording on the action's README and on the PR comment it posts. Copy only, no behavior change.

  • README tagline now describes what the actions do: check your OpenAPI specs for breaking changes on every pull request, post a side-by-side review as a PR comment, and (with Pro) approve or reject each change with a commit-status check that can block the merge.
  • PR comment + CI notices use standard GitHub terms ("status check", "check passes", "required check to block merging") for clarity.

reuvenharrison and others added 3 commits June 23, 2026 19:32
Reframe the tagline from detection-led ("comparing specs and detecting
breaking changes") to the product category: every PR becomes an API change
review (free: detect + post the review; Pro: approve/reject + merge gate).
Detection stays accurate, framed as what the free actions do. Matches the
oasdiff.com homepage hero.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The action README is an OSS/community surface; describe what the actions do
(check specs for breaking changes on PRs, post a side-by-side review, Pro
adds approve/reject + a merge-gating status check) rather than leading with
product positioning slogans. The 'API change review / code review for your
API contract' framing stays on the marketing site.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
EOF
)
The PR comment + CI notices are community surfaces. Replace our coinage
('merge gate', 'gates merge') with standard GitHub terms a developer expects:
'status check', 'check passes', 'required check to block merging'.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@reuvenharrison reuvenharrison changed the title readme: lead with the API Change Review positioning action: community-fit framing for the README + PR comment Jun 23, 2026
@reuvenharrison reuvenharrison changed the title action: community-fit framing for the README + PR comment README and PR comment: clearer, standard wording Jun 23, 2026
@reuvenharrison reuvenharrison merged commit fd0488b into main Jun 23, 2026
62 checks passed
@reuvenharrison reuvenharrison deleted the content/readme-api-change-review branch June 23, 2026 16:57
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.

1 participant