Repository navigation
Document public CI setup and prepare the math split decision - #247
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provide the public CI configuration and deployment recommendations requested by #216: define test scope, choose an execution environment, configure workflows, validate success/failure behavior, document operations and maintain the setup. Link verified project examples and primary GitHub guidance. This is documentation, not infrastructure deployment or a new foundation policy.
Add a short oneMath domain-split discussion brief after the WG co-chair confirmed that a new WG decision is needed. Preserve the June 2024 agreement and keep #126–137 open. Link the twelve tasks and the decisions needed to proceed.
Validation: local file/section links, document structure and whitespace checks pass. Required GitHub checks must pass before merge. No PDFs, project implementations, runner settings or governance decisions changed.
After merge, close #216 as the requested documentation delivered; deployment/ownership tasks remain separate. The user authorized pushing and merging after checks. Use the existing administrator review exception; this is not independent CODEOWNER approval.