[02:11:33] Universal Omega has reviewed your PR btw with comment [08:34:46] [1/3] MultimediaViewer has added two mobile components starting from 1.47, which can be enabled via `$wgMediaViewerMobileCarousel` and `$wgMediaViewerMobileBeta`. Do we need to test them on Mirabeta? [08:34:46] [2/3] https://www.mediawiki.org/wiki/Extension:MultimediaViewer#Image_Browsing [08:34:46] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1570718553227661363/97230696f9134c9a.png?ex=6af81d25&is=6af6cba5&hm=166d05f848d711c5c73823ccbfb4075cd92f6eb1e463317e957bce8da51f5e4b& [08:36:33] We can add them to mw-config in a PR and then ask someone to deploy that PR on beta so that you can test it? [08:38:55] [1/2] This is the workflow in my mind: metal_pail creates a task and submits a PR to mw-config -> someone with beta access deploys that PR -> metal_pail is able to test the PR on mirabeta [08:38:55] [2/2] I can fill in any of these steps if needed, but it'll be nice if newer folks can get some more practice [10:12:14] if new folks want practice could someone deploy latest upv2 and my related prs? [10:12:59] [1/2] https://github.com/miraheze/MirahezeMagic/pull/688 [10:12:59] [2/2] https://github.com/miraheze/mw-config/pull/6630 [10:28:12] [1/2] @elisapoly @suzuneu ^ if any of you is interested [10:28:13] [2/2] This is more complicated than a usual deploy because l10n strings are involved. If there are l10n changes in an extension, use the `--l10n` option of mwdeploy. [14:17:37] trying [14:22:07] @posix_memalign @honoka55 done, I believe [15:27:40] yeah i updated it [15:40:47] [1/2] somehow there's still the `'check '` problem [15:40:47] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1570825766067773440/image.png?ex=6af880ff&is=6af72f7f&hm=d53acbb09c2cb467205bc42c849a4eb080eab9c5edf4e44e591a1e13f8a08605& [15:41:37] [1/2] but yes my pr to add more social icons works well [15:41:37] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1570825972872126587/image.png?ex=6af88130&is=6af72fb0&hm=8593cb7d86e93243fe3b34b1af2f67ba2c849c8c5b8610fd51f0bbf3011382f8& [15:41:44] thank you! [16:25:19] has this been added to miraheze [16:28:04] oh i didn't find a log in #tech-ops [16:29:43] [1/2] oh yes this commit hash is exactly the one before it is fixed [16:29:43] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1570838078560538664/image.png?ex=6af88c76&is=6af73af6&hm=1e76e97d0b7c84ac8dc5c5a815f21f7b82624088a8a9073a0a94b99af18b1111& [16:30:29] @suzuneu could you also upgrade upv2? that's what i mean by deploy latest [16:31:50] oh since it's approved it can also be upgraded on prod tho nothing will happen [16:42:05] but i guess i'll finish this pr this weekend [16:42:34] it's already working so i just need to add more services [17:09:50] btw would any tech member like to review my current changes in the prs? i guess it will be more cluttered after i add more services [20:31:35] In MirahezeMagic, the messages don't need to go into overrides since they are new instead of being provided by UPV2. You can put them in https://github.com/miraheze/MirahezeMagic/blob/main/i18n/miraheze/en.json and then they no longer need to be repeated in the PHP files.