Repository navigation
feat(wporg): file issues in the pro repo when the product has one, else the free repo - #113
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.
Issues are filed in the product's -pro repo if it has one, otherwise in the free repo (
issue_reposin wporg/config/products.json, replacesfallback_repos). Code is still read from the free repo (the forum is about the free edition). The agent searches both repos for existing issues, since Crisp files free-edition issues in the free repos.The old probe-and-fall-back-to-pro behavior is removed: the job now only checks write access to the chosen issue repo and fails loudly if missing (no silent fallback). Verified the routing locally for a plugin, a theme with pro, and a free-only theme. 28 tests pass; not yet run in Actions.