Uh oh!
There was an error while loading. Please reload this page.
Move gh-pages into main branch - #3868
Conversation
…OpenAPI-Specification.git:gh-pages
gh-pages; Draft registry content
Add v3.0.2 respec/html
gh-pages; update index.md
[gh-pages] Hand-craft API templates for leaner output
Signed-off-by: Mike Ralphson <mike.ralphson@gmail.com>
Make 3.1 schemas retrievable from their $ids
Add v3.1 2021-05-20 schemas to website
Signed-off-by: Mike Ralphson <mike.ralphson@gmail.com>
Signed-off-by: GitHub <noreply@github.com> Co-authored-by: webron <webron@users.noreply.github.com>
* Added formats to the registry as defined by OpenAPI v3 * Fixed date-time format * Removed boolean as format is not needed
lornajane
commented
Jun 3, 2024
I don't have the permissions needed. I see the source, but not the branch picker. How can we test this before we do it? Did you try it out on o a public fork, or who can do that? I expected the |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Bellangelo
commented
Jun 4, 2024
@lornajane My bad. My fork is the https://github.com/Bellangelo/OpenAPI-Specification which deploys to the https://bellangelo.github.io/OpenAPI-Specification/. I have made some extra changes to the deploy / build scripts based on some finding from @ralfhandl . If you check this action https://github.com/Bellangelo/OpenAPI-Specification/actions/runs/9375129267 you can see that it passes. The way I have been testing the changes in the site so far is mainly using the fork. The fork copies also some repo settings about the deployment but you have to fork through the Github's UI. If you do this, you will be able to deploy the same way we deploy here but in our own url. |
Uh oh!
There was an error while loading. Please reload this page.
ralfhandl
left a comment
There was a problem hiding this comment.
Tested on a fork, respec workflow and github pages work fine
frankkilcommins
commented
Jun 12, 2024
I've created issue OAI/Arazzo-Specification#207 on the Arazzo repo to change our respec job so that it will work with the new structure. |
frankkilcommins
commented
Jun 12, 2024
Also note that #3900 will need to be incorporated into this PR if it's merged prior to this PR. |
lornajane
commented
Jun 30, 2024
@Bellangelo just wanted to drop you a note to say we haven't forgotten about your excellent work, just a lot of moving parts. We will figure it out. |
lornajane
commented
Oct 31, 2024
Sorry, closed the wrong PR! |
ralfhandl
commented
Nov 28, 2024
TDC decision: @ralfhandl to copy relevant instructions to #3717 and then close this PR. |
This comment was marked as spam.
This comment was marked as spam.
handrews
commented
Dec 2, 2024
I got impatient and copied the info over so we could reach zero open PRs 😁 |
Closes#3717
What I have done:
gh-pagesand move all files under thedocsfolder which Github supports.mainbranch and rungit merge gh-pages --allow-unrelated-histories. This merged the 2 branches even if they had unrelated histories.What we need to do after merge:
Settings>Pagesand under theBranchsection select themainbranch and thedocsfolder`.gh-pagesfor a few weeks, just to be able to quickly change in case of a bug in the process, and then we delete it.How to review
To quickly skip and verify the updated files, just follow the
What I have donesection and then you can justgit diffto distinguished what files have been moved and what files contain actual changes.