discourse/db/post_migrate
Martin Brennan dcf6da9cef
UX: Allow more specific enabled for options for upcoming changes (#39916)
Certain upcoming changes do not make sense to enable for "Everyone",
like changes that will only affect the admin UI. We currently have
a disallow_enabled_for_groups option that changes the "Enabled for"
dropdown to only show Everyone and No one, but this is a bit of a blunt
instrument.

This change adds an `allow_enabled_for` option for upcoming changes
which is a YAML array:

* When omitted, the "Enabled for" dropdown will show Everyone, Staff,
Specific group(s) and No one.
* When set to everyone, the dropdown will only show Everyone and No one.
* When set to staff, the dropdown will only show Staff and No one.
* It can also be set to staff and specific_groups

This commit also changes the reporting_improvements upcoming change
to be staff, specific_groups and adds a DB migration to account for
this.
2026-05-13 10:22:06 +10:00
..
20260112082200_drop_reviewable_action_logs.rb DEV: Remove reviewable_ui_refresh feature flag and legacy code (#36752) 2026-02-23 10:45:36 +08:00
20260311064518_clean_existing_tag_localization_names.rb FIX: Clean localized tag names (#38488) 2026-03-12 12:54:50 +08:00
20260319054730_delete_redundant_everyone_posting_review_groups.rb FEATURE: Support group based category posting review modes (#38707) 2026-04-07 10:41:16 +08:00
20260319054731_drop_permission_from_category_posting_review_groups.rb FEATURE: Support group based category posting review modes (#38707) 2026-04-07 10:41:16 +08:00
20260330161714_drop_pinned_post_number_from_nested_topics.rb FEATURE: First iteration of nested replies (#38888) 2026-04-16 08:06:44 -05:00
20260512061336_convert_reporting_improvements_everyone_to_staff.rb UX: Allow more specific enabled for options for upcoming changes (#39916) 2026-05-13 10:22:06 +10:00