Repository navigation
Remove retired VPS execution guidance from research guardrails - #88
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
Remove the obsolete VPS-specific testing advice and point scheduled advisory reviews to the existing GitHub-hosted monthly workflow. This changes documentation only and preserves the research-only, synthetic-test and private-data constraints.
Verified replacement:
.github/workflows/monthly_advisory_review.ymlruns onubuntu-latest; the report-build and artifact-upload steps succeeded in run 36910320463 on October 1. This evidence covers the monthly hosted job only; the separate weekly failure is not claimed fixed.Validation: reviewed the one-line diff, checked the relative workflow link and git diff --check. Required CI must pass at the locked head before a normal squash merge. No workflow, strategy, broker, deployment, authentication or runtime configuration changes.