BE Add Gitlab.com gold trial callout to /billings
CE port: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25482
What does this MR do?
-
Refactors callout helpers to render methods
-
Adds callout helper and ID for billing gold trial
-
Hides the callout if the current namespace is on a gold plan or trial.
-
Adds namespace plan matcher methods to Plan.
Table of MRs
• master
└── BE - billings-gold-trial-callout - ee!9610
└── FE - billings-gold-trial-callout-fe - ee!9611
├── FE - refactor dashboards - billings-gold-trial-callout-fe-dashboard ee!9644
├── FE refactor callout instantiation - billings-gold-trial-callout-fe-persistent-callout - ee!9647
└── BE - user_callout namespace migration - add-namespaces-to-callouts - ee!9807
└── FE+BE user_callout namespace - billings-gold-trial-callout-namespace-callouts - ee!9809
This is the branch setup, it is also the merge order. Every branch can be merged into the new master created from merging its parent. This stops everything bunching up into a single feature branch before hitting master.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /ee
folder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan? -
Security reports checked/validated by reviewer
Edited by Luke Bennett