We don't allow changes to existing OAuth apps; even for minor changes, the owner must register a new app. This is not great but also not easy to fix; a quick and dirty improvement would be to add a "create a new app based on this existing app" option, which would pre-fill the app registration form with the details of the old app.
Description
Details
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| OAuthConsumerRegistration: Add "copy" action to pre-fill propose form | Kwtbmmrnwnymy0 | mediawiki/extensions/OAuth | master | +84 -7 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T103587 Improve OAuth application approval workflow | |||
| Open | None | T426891 Create a new OAuth app based on an existing OAuth app |
Event Timeline
Change #1290105 had a related patch set uploaded (by Kwtbmmrnwnymy0; author: Kwtbmmrnwnymy0):
[mediawiki/extensions/OAuth@master] OAuthConsumerRegistration: Add "copy" action to pre-fill propose form
If we implement some kind of diff interface (T245290: OAuth consumer review interface should show changes from the last approved version) in the future, it would be nice to somehow expose "this app was based on that other app" to the admin reviewing the new app so they can diff them. Either via a new DB row, or by adding it into the log row.
Change #1290105 merged by jenkins-bot:
[mediawiki/extensions/OAuth@master] OAuthConsumerRegistration: Add "copy" action to pre-fill propose form
Partially done (thanks @KiwiTheMember). We'll probably want to allow copying another user's app as well.