Skip to content

fix a markdown error #2831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 23, 2021

Conversation

karenetheridge
Copy link
Member

No description provided.

@webron
Copy link
Member

webron commented Dec 20, 2021

Thanks for the fix. This needs to be submitted against the v3.1.1-dev branch as we don't make changes in published versions.

@karenetheridge karenetheridge changed the base branch from main to v3.1.1-dev December 20, 2021 23:40
@darrelmiller darrelmiller merged commit d8bf7d0 into OAI:v3.1.1-dev Dec 23, 2021
@karenetheridge
Copy link
Member Author

karenetheridge commented Dec 23, 2021

This needs to be submitted against the v3.1.1-dev branch as we don't make changes in published versions.

..but the published specifications were just changed in PRs #2798 and #2836 -- so this markup fix should be valid there too?

@karenetheridge karenetheridge deleted the ether/markdown-error branch December 23, 2021 19:24
@webron
Copy link
Member

webron commented Dec 29, 2021

@karenetheridge the source of truth of the file is the one found in the main branch. Once it reaches that branch, it is published and no longer touched (active work is done on *-dev branches). The PRs you referenced only affect the rendered version of the spec that appears at spec.openapis.org. That's just a reflection of the one in the main branch, but has the same contents.

charjr pushed a commit to charjr/OpenAPI-Specification that referenced this pull request Apr 27, 2023
charjr pushed a commit to charjr/OpenAPI-Specification that referenced this pull request Apr 27, 2023
@handrews handrews added this to the v3.1.1 milestone May 17, 2024
@handrews handrews added the bug label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants