Repository navigation
Conversation
This branch has not been deployed
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
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.
Bug 1428647: disable BMO-specific extensions
Disables the extensions that only make sense on bugzilla.mozilla.org by adding a 'disabled' marker, per comment 0: BMO, GuidedBugEntry, MozProjectReview, REMO, OrangeFactor, PhabBugz, ZPushNotify, ContributorEngagement.
Kept enabled (generic or depended on by generic extensions): Push (Webhooks depends on it), TrackingFlags (BugModal and BugmailFilter depend on it), Review, UserStory, and the remaining generic extensions. TagNewUsers, Profanivore, Bitly and BzAPI are borderline and left enabled; happy to disable any of them.
Core decoupling required to run without BMO
BMO monkey-patches methods onto core classes in its BEGIN block (Extension.pm lines 89-110), and several core call sites used them unconditionally. Each call site now checks ->can() first, following the same pattern as the secure_mail guard in PR #183:
The alternative would be core default stubs for these methods, with BMO overriding them under no warnings 'redefine'. I went with call-site guards to avoid adding new core API, but can switch if you prefer that approach.
Other fixes uncovered by disabling BMO
Test infrastructure
Results
Merge-order notes
Not addressed (separate follow-ups if wanted)