Skip to content

main: Create publishing PRs in new site repo #5046

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

main: Create publishing PRs in new site repo #5046

wants to merge 2 commits into from

Conversation

@ralfhandl
Copy link
Contributor

@ralfhandl ralfhandl commented Oct 17, 2025 •
edited
Loading

Create publishing PRs in new site repo OAI/spec.openapis.org instead of this repo:

  • Use app token for authentication
  • spec name in head branch name to avoid collisions between specs
  • base branch is main
  • Align reviewers with TSC and OpenAPI-maintainers teams
  • Consistent YAML formatting

Please check "Hide whitespace" when reviewing to minimize diffs.

Test PRs created by these workflows:

Counterpart to

  • no schema changes are needed for this pull request

@ralfhandl ralfhandl force-pushed the main-publish-to-separate-website-repo branch 2 times, most recently from e80e393 to 09ea209 Compare October 17, 2025 09:41
@ralfhandl ralfhandl linked an issue Oct 17, 2025 that may be closed by this pull request
Should we-organize our GitHub pages to a separate repo (by way of a directory on main)? #3717
Closed
This was referenced Oct 17, 2025
Closed
Closed
Merged
Open
@ralfhandl ralfhandl force-pushed the main-publish-to-separate-website-repo branch 2 times, most recently from f0235a3 to f6a4398 Compare October 19, 2025 13:53
@ralfhandl ralfhandl mentioned this pull request Oct 19, 2025
Draft
@ralfhandl ralfhandl force-pushed the main-publish-to-separate-website-repo branch from f6a4398 to 1f43a23 Compare October 22, 2025 15:52
@ralfhandl
Create PRs in new site repo
71e6c15 
- use app token for authentication
- spec name in head branch name to avoid collisions between specs
- base branch is main
- align reviewers with TSC and OpenAPI-maintainers teams
- remove mentions of gh-pages in other files
@ralfhandl ralfhandl force-pushed the main-publish-to-separate-website-repo branch from 1f43a23 to 71e6c15 Compare October 22, 2025 16:04
@ralfhandl ralfhandl added the script Pull requests that update Bash or JavaScript code label Oct 23, 2025
@ralfhandl ralfhandl marked this pull request as ready for review October 23, 2025 21:08
@ralfhandl ralfhandl requested review from a team as code owners October 23, 2025 21:08
@ralfhandl ralfhandl mentioned this pull request Oct 24, 2025
Open
@ralfhandl ralfhandl requested review from baywet and miqui October 24, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@miqui miqui Awaiting requested review from miqui

@baywet baywet Awaiting requested review from baywet

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

script Pull requests that update Bash or JavaScript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Should we-organize our GitHub pages to a separate repo (by way of a directory on main)?

1 participant

@ralfhandl