Portfolio: Mark LudicrousDB as GitHub-only - #97
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.
The repository owner confirmed LudicrousDB is distributed from GitHub, not WordPress.org, and authorized correcting its release policy. Change only the LudicrousDB inventory flag to
wordpress_org: falseand pin that decision with a regression assertion. The corresponding LudicrousDB manifest and AGENTS.md correction is stuttter/ludicrousdb#228; its metadata gate requires this immutable inventory change first. Local narrow tests and the full central test suite pass. No release credentials, workflows, or other plugin policies change.