feat: Add Stripe_id to Django Admin #1104
Conversation
|
This PR includes changes to |
| "marketing_name", | ||
| "base_unit_price", | ||
| "is_active", | ||
| "tier", |
There was a problem hiding this comment.
added tier and reordered the "billing" parts of the plan to be next to each other for slightly easier readability
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
|
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #1104 +/- ##
=======================================
Coverage 96.09% 96.09%
=======================================
Files 832 832
Lines 19501 19501
=======================================
Hits 18740 18740
Misses 761 761
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Purpose/Motivation
This PR adds the ability to add and update a stripe_id for a plan on django admin. The field is not required, as it's not used for free plans.
This will allow us to remove these things:
codecov-api/codecov/settings_prod.py
Lines 18 to 38 in c0110f8
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.