[02:45:39] Yeah, been noticing that even in Dayjob... It's not great [04:11:54] I tried to commit the changes SomeNWDev suggested in a PR, and I tried multiple times for each, after I manually added some it only worked for their last suggestion. [04:12:04] Drove me crazy. [06:38:32] [1/2] New Request for Feedback open for voting: [06:38:32] [2/2] https://meta.miraheze.org/wiki/Tech:Noticeboard/Request_for_feedback:_changes_to_default_MediaWiki_settings_(2) [14:10:13] if you have the changes locally then you can just do `composer fix` [14:30:54] [1/4] https://cdn.discordapp.com/attachments/1006789349498699827/1560661319114301560/DSC_0369.png?ex=6ad3869e&is=6ad2351e&hm=1b8e05f66ca0d6bdb24c3b54773e60805cf548c9d4beff02890b71c409fa527d& [14:30:55] [2/4] https://cdn.discordapp.com/attachments/1006789349498699827/1560661319596904478/image_2x81bo.png?ex=6ad3869e&is=6ad2351e&hm=4c7f2b4f7a665ff3d44e52086ae909d9903a110218ab08059e06789ed4020933& [14:30:55] [3/4] https://cdn.discordapp.com/attachments/1006789349498699827/1560661320087511050/IMG-20260918-WA2849.png?ex=6ad3869e&is=6ad2351e&hm=66b66bce5a4c403cdb40c2b10122bee31d5b292947992ba27835eebd121c2957& [14:30:55] [4/4] https://cdn.discordapp.com/attachments/1006789349498699827/1560661320511266826/DSC_2383.png?ex=6ad3869e&is=6ad2351e&hm=81abd669ae9fb23ac08c6f24e9f2de2e62e24daace697f29b7a54ea3280320ef& [14:49:35] Huh? [15:47:50] if CI fails [15:48:04] composer test and composer fix are the best ways to autofix things [15:48:09] That's not what I'm confused by. [15:48:14] Cause that's not what I was talking about. [15:48:16] I assume that's what jenny meant [15:48:24] I assume you mean though that github is just shit [15:48:36] cough https://mrshu.github.io/github-statuses/ [15:48:47] it has like 93% uptime [15:48:58] Yes, because when someone suggests a change in your PR, you can co-author a commit with them by adding their suggestions if they don't require any changes. [15:49:11] I hate co-authoring [15:49:12] But it didn't work for all but one time I tried it. [15:49:48] tbh I am starting to think phorge or gerrit are going to be the new things I use to host code [15:50:32] but pull requests are far more flexible [15:50:52] it's the devil, too useful to get away from but too bad to use [15:51:09] I wanted to self-host my own code through ForgeJo, but I don't wanna do that anymore. [15:51:35] if I had more time and resouces I would go run gerrit [15:51:44] Eh, Gerrit is a mess afaik. [15:51:46] but I don't trust using a single node to run gerrit [15:51:54] gerrit is actually quite nice [15:52:24] I don't like the whole one commit per patch model but [16:12:27] Worst software on earth [16:30:10] iirc that's just what the CI runs anyway, so you can run those commands locally if you want to check your PR [16:38:15] I know how the CI works. [16:38:17] That's not what I'm talking about. [16:48:07] Gerrit is a learning curve that you eventually love to hate [20:27:32] [1/2] Found an inconsistency in the edit request tab for wiki requests that WRs can see. "NSFW" is written as "not safe for work" and "not safe to work." [20:27:33] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1560751068802195536/image.png?ex=6ad3da34&is=6ad288b4&hm=675d05bfe98af7b16970c2a06d082aa407013dd1cb57feb7ecfe9d86af79a178& [20:32:13] Originates from https://github.com/miraheze/MirahezeMagic/blob/6fe3a71c8ef540d1b1a24863f05812ca7b35109d/i18n/miraheze/en.json#L133. Should be an easy fix. [20:45:13] In fact it shouldn't be too hard to fix it yourself if you'd like. GitHub has an okay interface for making small edits on a file. [20:51:16] I was about to, but it said it was read-only [20:51:55] It think it will prompt you to fork the repository? [20:53:05] If not then this is bad UX. [20:53:27] "Code view is read-only" (maybe because I'm not signed in and I can't find where I saved my password) [20:57:30] Just made a new account, and it still says that [20:58:06] [1/6] Could also be that. I think the workflow would be [20:58:06] [2/6] 1. Sign up/log in [20:58:06] [3/6] 2. Try to edit the file [20:58:06] [4/6] 3. If the edit fails, manually click fork on MirahezeMagic to fork the repository [20:58:07] [5/6] 4. Edit the file on the forked version [20:58:07] [6/6] 5. After the edit GitHub should automatically give a prompt/notice about submitting a pull request [20:59:32] [1/2] I think I'm starting to do it right now [20:59:32] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1560759121488384010/image.png?ex=6ad3e1b4&is=6ad29034&hm=55d3d57f8bf9a8475708118929fcf8b4e7a9c899abf90017fa52c491768b6d45& [21:03:00] [1/2] @posix_memalign [21:03:00] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1560759993878183977/image.png?ex=6ad3e284&is=6ad29104&hm=3a87c9a506af8bc59661a91dd4590d8762cffdd63f889c58219bb50ae19e1c37& [21:05:29] https://github.com/miraheze/MirahezeMagic/pull/673 [21:11:00] Thanks for the PR. Merged. Will deploy shortly. [21:42:17] I’m trying to log in to Phorge and I’m being told the DB is in read only mode. Is this expected? [21:52:13] Yes [21:52:23] Something something moving to a new server or something [21:55:03] you should be able to now [22:02:33] db is being migrated to the new db193 in an effort to address the disk space issue on db182 [22:56:58] I like Gerrit, but it's definitely not for everyone.