-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add watchlisting options for autowelcome #670
Comments
Global preferences would have to be taken into account also if we take this on. |
Global preferences are somewhat meaningless here; at the moment we default to the user's on-wiki preferences for editing a page, by virtue of not telling MediaWiki what to do with the watchlist. MediaWiki decides whether or not to add the page to the user's watchlist. We can override this on a per-edit basis (in other words, whenever we do an auto-welcome) really easily, by just adding the relevant parameters to the page edit request, specifically |
Support this - I don't have WP set up to watchlist every edit, but rather have Twinkle set to temporarily watchlist anyone I welcome. It would be nice (though certainly not critical) to be able to set up ACC to do the same. |
No longer needs schema changes following preferences refactor |
If someone else wants to pick this up, #566 has guidance on adding new preferences. With the guidance for where and what to change to set the watchlist preferences in the comment above, this should be doable by someone other than me. 😀 I'd suggest a dropdown in preferences for possible options ranging from "Use on-wiki preference", "Don't watchlist", "Watchlist permanently", and a reasonable range of "Watchlist for X time" options. |
This is not a pressing issue by any means, but with autowelcoming incoming, it would be nice to have a feature that overrides the enwiki autowatchlisting preferences and allows users to have the option of selecting whether they want to (temporarily or indefinitely) watchlist the talk pages of accounts they created.
The text was updated successfully, but these errors were encountered: