Page MenuHomeMiraheze

Add better CI for MediaWiki standards
Closed, InvalidPublic

Description

A better CI should be built for our own extensions to maintain better code quality by using the MediaWiki standards.

I am working on this implementation.

Event Timeline

Universal_Omega created this task.
Universal_Omega moved this task from Backlog to Maintenance on the GlobalNewFiles board.
Universal_Omega moved this task from Backlog to Maintenance on the IncidentReporting board.
Universal_Omega moved this task from Backlog to Maintenance on the ManageWiki board.
Universal_Omega moved this task from Backlog to Maintenance on the MatomoAnalytics board.
Universal_Omega moved this task from Backlog to Short Term on the MediaWiki (SRE) board.
Universal_Omega moved this task from Backlog to Maintenance on the RemovePII board.
Universal_Omega moved this task from Backlog to Maintenance on the RottenLinks board.
Universal_Omega moved this task from Unsorted to Goals on the Universal Omega board.
Universal_Omega moved this task from Backlog to Maintenance on the WikiDiscover board.

https://github.com/miraheze/ManageWiki/pull/297 does this for ManageWiki, implementing eslint, stylelint, and phpcs. It also will make GitHub Actions automatically commit formatting fixes, when possible.

I've extended the above mentioned PR to now also include phan.

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

9 different software components = 9 different tasks surely? They just good task management and makes things easily trackable and measurable.

It's probably better to be tracking things separately and have subtasks for each extension

In T7939#160072, @John wrote:
In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

9 different software components = 9 different tasks surely? They just good task management and makes things easily trackable and measurable.

Yeah that's probably a good idea. I will create a separate task for each. It's better for tracking anyways. I'll do that shortly. Although it is one end-objective, closing each task individually when completed is likely better for tracking purposes.

@RhinosF1 Tracking the progress is the reason I created this task rather then just doing it without a task, and separate tasks is likely better for that.