martin
(Martin Brennan)
Mai 13, 2026, 12:24
28
@Michelle_L , je viens de fusionner une modification pour clarifier cela :
main ← ux/upcoming-change-enabled-for-groups
merged 12:22AM - 13 May 26 UTC
Certain upcoming changes do not make sense to enable for "Everyone",
like chang… es 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.
<img width="1118" height="215" alt="image" src="https://github.com/user-attachments/assets/506674d5-713e-44f8-a57d-428818733ab0" />
Une fois cela déployé sur votre site, les options de l’amélioration à venir de la fonctionnalité de signalement seront uniquement « Personne », « Équipe » et « Groupes spécifiques », comme suit :
2 « J'aime »