Hmm, this still mixes an actual implementation (parameter action) with some outcomes of specific values (info, purge) passed to that implementation; plus how to differentiate / distance from action=edit (MediaWiki-Page-editing), action=history (MediaWiki-Page-history), etc?

action=info is basically the result of the special page Special:PageInfo?

To me purging has been somewhere unclear between MediaWiki-File-management, MediaWiki-Page-editing and MediaWiki-General. Maybe it should even have its own tag. But preferably not under a #MediaWiki-Actions umbrella? (I know MediaWiki-Special-pages exists, we shouldn't repeat that mistake.)

In T268386#6638452, @Aklapper wrote:

Hmm, this still mixes an actual implementation (parameter action) with some outcomes of specific values (info, purge) passed to that implementation; plus how to differentiate / distance from action=edit (MediaWiki-Page-editing), action=history (MediaWiki-Page-history), etc?

Perhaps create #mediawiki-action-purge / #mediawiki-action-info / #mediawiki-action-credits for the actions that don't have dedicated components related to their underlying code?

action=info is basically the result of the special page Special:PageInfo?

Special:PageInfo just redirects to action=info

Any input from CPT?

I think this project as proposed might be too generic. Apart from a very basic set of interfaces and wiring, the Action system isn't much, and also doesn't have an owner currently. Might be small and simple enough to keep under generic with teams tagge as-needed. At least that way it's clear that something isn't tracked by anyone.

I do support the idea of connecting MW's built-in actions to existing features, and creating them if missing.

• "Edit" - MediaWiki-Page-editing
• "History" - MediaWiki-Page-history
• "Patrol" – MediaWiki-Patrolling
• "Delete" – MediaWiki-Page-deletion
• "Purge" - This is a tiny wrapper around code that largly falls under MediaWiki-Page-derived-data and HTTP Cache (MediaWiki-libs-BagOStuff). There is a similar tiny wrapper for it in the action API. Perhaps it could be documented as part of Mediawiki-Page-derived-data?
• "Info" - This indeed doesn't have a project gag or owner currently. All sorts of data from different features is exposed through here, but perhaps the UI itself is worthy of its own project tag (perhaps MediaWiki-Page-info)

This isn't useful to Platform Engineering, but we are not opposed to this if it's useful to someone.

Proposing to decline per Krinkle's comment...