Dev #220
Merged
Dev #220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t proper filtering)
and turn assertion into a warning
This reverts commit 85380b5.
…r suffer from mediacloud volume regression related issues
…END_RESOLUTION env var this is useful to set different resolutions on staging and production
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
railway-app
bot
temporarily deployed
to
media-impact-monitor-pr-220
|
🚅 Deployed to the media-impact-monitor-pr-220 environment in media-impact-monitor
|
railway-app
bot
temporarily deployed
to
media-impact-monitor-pr-220
railway-app
bot
temporarily deployed
to
media-impact-monitor-pr-220
|
@davidpomerenke thx! This is fine for the frontend! I will merge it once the tests pass... :) After this I should be able to use the production API right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have now fixed failing tests in the backend, so that we could now deploy it to the production API URL by merging dev into main again.
Is this also okay regarding the frontend? @vogelino