Closed ColinBuyck closed 3 days ago
Name | Link |
---|---|
Latest commit | f09d749abf657585e6760cc980aa84eb6096b311 |
Latest deploy log | https://app.netlify.com/sites/partners-bloom-dev/deploys/66e8da1e44056c0008c5efce |
Deploy Preview | https://deploy-preview-4317--partners-bloom-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | f09d749abf657585e6760cc980aa84eb6096b311 |
Latest deploy log | https://app.netlify.com/sites/bloom-exygy-dev/deploys/66e8da1eeb94b70009db8f06 |
Deploy Preview | https://deploy-preview-4317--bloom-exygy-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This PR addresses #4053
Description
In pulling the lottery env to Doorway, I noticed that the public show_lottery flag would overlap with the partners show_lottery flag in the docker builds. Through discussions with Emily, it's clear that admin will want the option to experiment with the lottery features without it being visible to the public users. This updates the env name and adds additional checks to make that separation possible.
How Can This Be Tested/Reviewed?
Provide instructions so we can review, including any needed configuration, and the test cases that need to be QAd.
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: