Note that this proposal is distinct from T303342: Users get an automatic edit tag when publishing that shows what kind of edit was made, and we probably shouldn't do both.

Idea: To help people filter RecentChanges and review edits more easily, we should use edit tags to explain what kind of Object was edited.

Pros:

• This would help people look only for edits to Functions, or to Types, or whatever they care about.
• The filtering system is standard and well-supported, and wouldn't need extra work for this.

Concerns:

• This is a conceptually "wrong" use of Edit tags – we're not annotating the edit, we're annotating the page. MW doesn't provide that concept, however. MW/Editing might have some objections to this use pattern, and we should check with them first.
• This would mean every edit to an Object would get tagged, which might be irritating to users (e.g. on Functions' history pages, every edit would be tagged that they were editing a Function, which would crowd out information). By doing this, we're tilting the system behaviour in favour of users of RecentChanges and against users of history pages.
• There are system stability limits to how many edit tags can be used, so if we're doing this, we'd need to decide on a very limited number of Types to tag (e.g. Function, Implementation, Test case, Type, and Other).