491:
688:
471:
55:
642:, which basically involves one-param-per-line and piping fixes. Specifically, I'd be fixing 1.a (moving pipes to the left of params), 1.b (one param per line), 1.c (extra pipe removal), and 2.d (empty line removal). This isn't critical to the running of the task, but since it seems to be working pretty well I figured I'd do some cleanup while I was at it.
333:
As seen in my previous bot runs, I have a lot of past experience with removing deprecated/unnecessary/etc parameters from templates. With this number seemingly increasing (4 of the last 5 BRFAs were for this purpose) I thought I would get an open-ended approval for this task. The general criteria for
399:
your methodology. Getting a list of parameters from the editor(s) leading the merge effort will be useful to show that the bot is performing a consensus-based task. With regard to your first criterion, it might need to be tweaked a bit to be applicable to the
Infobox UK school to Infobox school
523:
I checked about 50 of the 250 edits, and they all looked fine to me. Except for a page blanking that
Primefac will implement a fix for, none of the templates were broken or degraded in any way. (I put a note on Primefac's talk page requesting a minor enhancement, but implementation of that
370:, which basically involves one-param-per-line and piping fixes. Specifically, 1.a, b, c, and 2.d - I never did get around to investigating the others. This logic makes the actual task of tweaking params a lot easier, hence my interest in including it.
449:
the running of this bot, Primefac does have a lot of past experience with removing deprecated/unnecessary/etc parameters from templates as noted above and has done bot runs for me in the past for
Infobox school which was excellent and really helpful.
400:
merger: the bot's work will migrate current parameters in a TfD'd infobox to supported parameters in the merge target, thereby avoiding the creation of 1000+ unsupported parameters when the TfD'd infobox is turned into a redirect. –
627:, I understand you want it to also be "+AWB genfixes" which overall isn't an issue if that is what it is supposed to be doing. Can you talk more about what the special added "infobox genfixes" are? —
591:
The genfixes were thrown in during tasks 28 and 29, and are just AWB's standard genfixes. I have no issues disabling them if that's a concern. I will note, however, that the addendum is
733:
379:
279:
275:
271:
267:
263:
259:
255:
378:
As a note/thought, this would also be used/useful for when TFD mergers are implemented, which is really what motivated me to file this BRFA as I might have been stretching
251:
247:
348:
A list (ideally created by the requesters and not myself, but I will do it if necessary) will be created for the parameters to be removed/changed/updated/etc
345:
Discussion must be present and consensus agrees that a bot run will be necessary to remove the bad params (e.g. see discussions for bot runs 28 and 29)
502:
352:
21:
159:
94:
506:
147:
89:
475:
Approved for trial (250 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
666:
283:
124:
638:
Oh, right, forgot I wrote that. I mentioned it briefly in the
Function details, but I'll elaborate. It is based on
290:
676:
546:
455:
171:
109:
700:
680:
651:
633:
608:
586:
550:
533:
518:
484:
459:
438:
424:
409:
391:
715:
47:
639:
367:
211:
468:. "Voting" here is not needed. As far as the task - the criteria are very clear, and well thought out.
672:
542:
451:
224:
165:
104:
625:
Function overview: Remove deprecated/invalid parameters from templates as well as "infobox genfixes"
153:
99:
529:
434:
405:
647:
604:
514:
420:
387:
141:
84:
17:
238:
525:
430:
401:
356:
727:
695:
643:
628:
615:
600:
581:
563:
510:
482:
416:
383:
317:
136:
65:
366:
As a result of the last two bot runs (28/29) I also worked out most of the kinks in
505:. As a note, I was informed of the one edit that blanked the page (I had forgotten
233:
27:
382:
a little farther than it should have been stretched on a couple of occasions.
538:
477:
355:
or some such location) fully documenting the previous three steps (i.e.
334:
running this bot would be something along the lines of the following:
307:
1000-8000 pages, depending on transclusion count and size of category
572:)? I'm seeing changes in your trial that are not about the infobox (
708:
The above discussion is preserved as an archive of the debate.
210:
Remove deprecated/invalid parameters from templates as well as "
714:
To request review of this BRFA, please start a new section at
568:
can you explain more what you are throwing in with this task (
338:
Template must have 1000+ pages in a "bad parameters" category
201:
46:
To request review of this BRFA, please start a new section at
362:
The parameters will be updated as dictated in the discussion.
351:
The specific task will be added to a "records page" (likely
577:
573:
498:
189:
183:
177:
119:
114:
79:
524:
enhancement should not block this bot's approval.) –
342:(anything smaller can really be cleaned up manually)
340:
and/or be a template merger with 1000+ transclusions
301:
As needed/requested, but each request will be a OTR
734:Approved Knowledge (XXG) bot requests for approval
244:Links to relevant discussions (where appropriate):
40:The following discussion is an archived debate.
640:Headbomb's proposed logic for infobox cleanup
368:Headbomb's proposed logic for infobox cleanup
8:
353:User:PrimeBOT/Parameter removal records
624:
7:
305:Estimated number of pages affected:
200:22:16, Monday, November 12, 2018 (
35:
218:Automatic, Supervised, or Manual:
52:The result of the discussion was
686:
489:
469:
53:
541:, is this ready for approval?
1:
701:18:21, 30 November 2018 (UTC)
681:17:41, 30 November 2018 (UTC)
652:21:16, 28 November 2018 (UTC)
634:03:39, 28 November 2018 (UTC)
609:21:05, 27 November 2018 (UTC)
587:20:46, 27 November 2018 (UTC)
551:18:49, 27 November 2018 (UTC)
534:19:28, 22 November 2018 (UTC)
519:19:10, 22 November 2018 (UTC)
485:09:29, 20 November 2018 (UTC)
460:20:03, 17 November 2018 (UTC)
439:15:11, 13 November 2018 (UTC)
425:11:15, 13 November 2018 (UTC)
410:05:30, 13 November 2018 (UTC)
392:22:18, 12 November 2018 (UTC)
509:), so that's taken care of.
750:
595:which is not the same as
711:Please do not modify it.
43:Please do not modify it.
507:to add in GreenC's fix
415:Good point. Updated.
22:Requests for approval
225:Programming language
18:Knowledge (XXG):Bots
667:BAGAssistanceNeeded
623:task overview says
318:Exclusion compliant
246:Previous bot tasks
570:"infobox genfixes"
284:current discussion
208:Function overview:
331:Function details:
291:infobox UK school
26:(Redirected from
741:
713:
698:
690:
689:
671:
665:
631:
619:
594:
584:
567:
493:
492:
480:
473:
472:
295:
289:
212:infobox genfixes
194:
193:
57:
56:
45:
31:
28:User:PrimeBOT/30
749:
748:
744:
743:
742:
740:
739:
738:
724:
723:
722:
709:
696:
687:
673:Steven (Editor)
669:
663:
629:
613:
592:
582:
561:
543:Steven (Editor)
495:Trial complete.
490:
478:
470:
466:This is not RFA
452:Steven (Editor)
376:
341:
299:Edit period(s):
293:
287:
139:
135:
130:
69:
54:
41:
33:
32:
25:
24:
12:
11:
5:
747:
745:
737:
736:
726:
725:
721:
720:
704:
703:
661:
660:
659:
658:
657:
656:
655:
654:
558:
557:
556:
555:
554:
553:
536:
444:
443:
442:
441:
375:
372:
364:
363:
360:
349:
346:
343:
339:
129:
128:
122:
117:
112:
107:
102:
97:
92:
87:
82:
80:Approved BRFAs
77:
70:
68:
63:
62:
61:
36:
34:
15:
14:
13:
10:
9:
6:
4:
3:
2:
746:
735:
732:
731:
729:
719:
717:
712:
706:
705:
702:
699:
693:
685:
684:
683:
682:
678:
674:
668:
653:
649:
645:
641:
637:
636:
635:
632:
626:
622:
617:
612:
611:
610:
606:
602:
598:
590:
589:
588:
585:
579:
575:
571:
565:
560:
559:
552:
548:
544:
540:
537:
535:
531:
527:
522:
521:
520:
516:
512:
508:
504:
503:documentation
501:, as well as
500:
496:
488:
487:
486:
483:
481:
476:
467:
464:
463:
462:
461:
457:
453:
448:
440:
436:
432:
429:Well done. –
428:
427:
426:
422:
418:
414:
413:
412:
411:
407:
403:
398:
394:
393:
389:
385:
381:
373:
371:
369:
361:
358:
354:
350:
347:
344:
337:
336:
335:
332:
328:
326:
323:
320:
319:
314:
312:
311:Namespace(s):
308:
306:
302:
300:
296:
292:
285:
282:, as well as
281:
277:
273:
269:
265:
261:
257:
253:
249:
245:
241:
240:
237:
235:
230:
228:
226:
221:
219:
215:
213:
209:
205:
203:
199:
195:
191:
188:
185:
182:
179:
176:
173:
170:
167:
164:
161:
158:
155:
152:
149:
146:
143:
138:
134:
126:
123:
121:
118:
116:
113:
111:
108:
106:
103:
101:
98:
96:
93:
91:
88:
86:
83:
81:
78:
76:
72:
71:
67:
64:
60:
51:
49:
44:
38:
37:
29:
23:
19:
710:
707:
691:
662:
620:
596:
569:
494:
474:
465:
446:
445:
396:
395:
377:
365:
330:
329:
324:
321:
316:
315:
310:
309:
304:
303:
298:
297:
243:
242:
232:
231:
223:
222:
217:
216:
207:
206:
197:
196:
186:
180:
174:
168:
162:
156:
150:
144:
132:
131:
74:
58:
42:
39:
593:(+genfixes)
234:Source code
198:Time filed:
66:PrimeBOT 30
599:genfixes.
374:Discussion
286:regarding
236:available:
220:Automatic
190:ANI search
184:rights log
172:page moves
160:edit count
120:rights log
110:page moves
692:Approved.
526:Jonesey95
431:Jonesey95
402:Jonesey95
178:block log
133:Operator:
115:block log
59:Approved.
728:Category
697:xaosflux
644:Primefac
630:xaosflux
616:Primefac
601:Primefac
583:xaosflux
564:Primefac
511:Primefac
417:Primefac
384:Primefac
322:(Yes/No)
148:contribs
137:Primefac
90:contribs
20: |
716:WT:BRFA
597:infobox
447:Support
397:Support
380:Task 24
48:WT:BRFA
278:, and
239:WP:AWB
580:). —
499:Edits
313:Main
95:count
16:<
677:talk
648:talk
621:this
605:talk
547:talk
530:talk
515:talk
456:talk
435:talk
421:talk
406:talk
388:talk
327:Yes
229:AWB
227:(s):
166:logs
142:talk
125:flag
105:logs
85:talk
75:BRFA
578:ex2
574:ex1
539:SQL
479:SQL
357:CYA
202:UTC
154:SUL
100:SUL
730::
694:—
679:)
670:}}
664:{{
650:)
607:)
576:,
549:)
532:)
517:)
497:-
458:)
437:)
423:)
408:)
390:)
294:}}
288:{{
280:29
276:28
274:,
272:26
270:,
268:23
266:,
264:20
262:,
260:18
258:,
256:10
254:,
250:,
214:"
204:)
718:.
675:(
646:(
618::
614:@
603:(
566::
562:@
545:(
528:(
513:(
454:(
433:(
419:(
404:(
386:(
359:)
325::
252:8
248:7
192:)
187:·
181:·
175:·
169:·
163:·
157:·
151:·
145:·
140:(
127:)
73:(
50:.
30:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.