Make all related onboarding areas use Gitlab::Saas.feature_available?
What does this MR do and why?
Make all related onboarding areas use the enabled method
- this either switches some from being just a .com check
to
Gitlab::Saas.feature_available?
, as they should... - or consolidate on using the enabled method as a way to tie together the onboarding theme to one SSOT
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #413521 (closed)
Edited by Doug Stull