Skip to content

docs: revert oasdiff.yaml configuration section pending move to .oasdiff.*#113

Merged
reuvenharrison merged 1 commit intomainfrom
docs/revert-oasdiff-yaml-section
May 8, 2026
Merged

docs: revert oasdiff.yaml configuration section pending move to .oasdiff.*#113
reuvenharrison merged 1 commit intomainfrom
docs/revert-oasdiff-yaml-section

Conversation

@reuvenharrison
Copy link
Copy Markdown
Contributor

Summary

Reverts the "Configuring with oasdiff.yaml" subsection added in #110/#111. The documented filename (oasdiff.yaml at repo root) is unconventional for a CI/lint tool — most tools in this category use a dotfile (.eslintrc, .prettierrc, .golangci.yml, .yamllint, .flake8, .markdownlint.json).

Pulling the docs section now so customers don't adopt the unconventional path during the brief window we recommended it. The CLI's config-file lookup will move to .oasdiff.* in a follow-up; documentation will return at that point with the right path.

What stays

Companion reverts

  • oasdiff/w3#??? — same-shape revert of /docs/github-action page.
  • oasdiff/oasdiff#??? — drop the cross-link added to CONFIG-FILES.md.

Test plan

  • Read the rendered README on GitHub
  • Confirm the TOC still scrolls to the right sections
  • Confirm the Free actions block ends after the diff action and goes straight to "Spec paths"

The documented path (oasdiff.yaml at the repo root) is unconventional
for a CI/lint tool. Most tools in this category use a dotfile
convention (.eslintrc, .prettierrc, .golangci.yml, .yamllint, etc.).

Pulling the section so customers don't adopt the unconventional path
and have to migrate later. The CLI lookup will move to .oasdiff.* in
a follow-up; documentation will return at that point with the right
path.

Keeps the rest of the README intact: the TOC structure (only the line
for this removed section is dropped), the boolean-limitation wording
fix from #111, all action subsections.
@reuvenharrison reuvenharrison merged commit daa39a7 into main May 8, 2026
24 checks passed
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