-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change BrewRenderer background in Heroku test deployments #3688
Change BrewRenderer background in Heroku test deployments #3688
Conversation
What issue is this trying to solve? |
This is trying to help us in the development, so we don't confuse local vs deployment vs live. Minor inconveniences. |
Can we get a deployment on this one to validate? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Need to see the deployment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, deployment works great for the intended use.
@G-Ambatte Can you address 5e-Cleric's open comment and resolve conflicts, and then I can merge this. |
I've implemented the suggested change... which led me to investigate if |
Nice added cleanup. Merging! |
This PR modifies the BrewRenderer to change the default background when the
HEROKU_APP_NAME
variable exists. This variable only exists when created during the PR deployment process in Heroku apps, or when specifically set on a Development machine.The main purpose of this PR is to create a visual indication that someone is working on a deployment, NOT the main website. This is primarily intended to be a Dev Experience QoL improvement, which is why I've marked it as a low priority change.