[14:33:36] how can I "remove" an project link in the navigation and make it only visible for specific users? [15:04:55] Is transclusion possible across interwiki links? [15:09:49] In theory https://www.mediawiki.org/wiki/Manual:$wgEnableScaryTranscluding [15:27:49] we use transclusion by interwiki, but it's often not as nice as you'd think :P [15:28:29] it does work, but I don't think it's a very well-supported feature [15:28:45] Well, the name hardly inspires confidence ;) [15:44:06] It does seem to be a lot more work than what I want to do [15:45:09] I'm just want to take a couple words of text from one user subpage to my user subpage on a different wiki [18:27:00] How would I typically implement a phpunit test for a Job? Job as in https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers [18:29:30] Have a look at the ones in core? [18:29:38] CategoryMembershipChangeJobTest.php etc [18:29:59] Thanks, I'll take a look. [22:35:28] hey. I'm looking to pick up an abandoned change. it has a bunch of patches in it already. I suppose I should just add to this change (that's what another contributor tried to do, before they dropped it too). I'm guessing that's classed as amending a change for the purposes of https://www.mediawiki.org/wiki/Gerrit/Tutorial#Amending_a_change_(your_own_or_someone_else's)? [22:35:56] If so, do I need to request to be in the Trusted-Contributor group? [23:24:54] ProcReader: infortunately, yes [23:25:24] saper: no way I can 'fork' this commit somehow, and push a separate commit? [23:25:43] ProcReader: which change is this? [23:25:44] well, poor terminology, more like just pull, checkout, create new branch from that, rebase it and go from there? [23:25:50] uhh, one moment [23:26:00] https://gerrit.wikimedia.org/r/218104 [23:27:20] ProcReader: can you write a comment there (whatever the text)? [23:28:15] done [23:30:33] just a see [23:30:35] sec [23:33:16] ProcReader: try to push, I think I have added you to that group [23:38:04] thanks! will try after I finish merging. so I presume it's preferred to add patches to this one, rather than create a new commit? saper [23:39:54] it works like this - you have fetched the latest patch of the change, in this case 2de18c76193ba11c32d5ba122ac1585f1edc87d1 [23:40:38] you can try to "rebase" this one and then do your changes on top of that (with "git commit --amend") [23:46:12] saper: yup, what I mean is would it be preferred for me to add onto Cenarium's change rather than create a new one? [23:49:19] ProcReader: depends what you are changing - if this is an update to this feature, then yes [23:49:46] but do not introduce unrelated changes this way [23:49:51] ideally finish it off, not sure how much was left [23:51:05] great, go for it... [23:56:57] saper: if I can ask, any idea on what might be the best way to merge these, given 3 years of commits on master in between?