Add a build system including an empty spec and trivial schema#1
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
|
OK apparently there's no way to get GitHub to run CI before this is merged. Why it seems to run CI just fine on build-infra's first PR I don't know, but most of this is boilerplate and literally nothing depends on this repo, so once OAI/build-infra#1 is merged, if the boilerplate looks good we can merge it and open another PR (e.g. writing a real README) to make sure CI passes. Note that like OAI/build-infra#1, this was written by Codex with GPT 5.5. |
|
Force-push just amends the build-infra commit to which we point as OAI/build-infra#1 has been updated with new commits. I can also do these commit updates as additional commits if we don't mind potentially having a long string of commits here that just change the build-infra commit hash. |
Co-authored-by: Codex <codex@openai.com>
|
This has been replaced by PR #2. |
Replaced by PR #2
This Codex-written PR sets up this repository for specification development. It is a draft because it depends on OAI/build-infra#1, although in theory the CI should pass here as the target commit exists in that repo even though it is not yet on main. See documentation in that PR for details on how this works.I have prepped the same PR for sig-security, and a migration PR for OpenAPI-Specification, but let's see how this goes here before tackling more repositories.