Last modified: 2014-07-03 12:45:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13516 - Interface support to mark bot edits in histories
Interface support to mark bot edits in histories
Status: NEW
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 11181
  Show dependency treegraph
Reported: 2008-03-26 10:35 UTC by とある白い猫
Modified: 2014-07-03 12:45 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description とある白い猫 2008-03-26 10:35:58 UTC
Actually while discussing this idea with Pathoschild something interesting came
about. Why not prod the issue a bit further. The code could add a "bot"
(variable - so that it can be translated to the local language) to the bots

Current history line (from

16:56, 2 September 2007 Ordinateur (Talk | contribs) m (43 bytes) (Robot :
répare double redirection) (undo)

how it would be:

16:56, 2 September 2007 ([[link to what a wikipedia bot is|Robot]]) Ordinateur
(Talk | contribs) bm (43 bytes) (Robot : répare double redirection) (undo)

One or two Mediawiki namespace pages can deal with this.


I was told to propose this separately on bug #11162 (comment 3)
Comment 1 Andre Klapper 2014-07-03 12:45:38 UTC
I'm tempted to mark this as a duplicate of bug 16228, though it's not exactly the same. Or I fail to see the exact difference to bug 11181.

Note You need to log in before you can comment on or make changes to this bug.