-
Notifications
You must be signed in to change notification settings - Fork 17
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
Extend feature environments with frontend #203
Comments
Ideally, if we will have a comand that will triger test env, it can be a branch mentioned in this command. |
Blocked until frontend implements the new version of API CC @hcho112 ping us when you guys think its ready to be deployed |
Is this ready now? |
Looks like we will change our design to have only one test environment. It will be updated on request from any PR. |
Since we are moving to a static feature enviornment I agree that we can close this |
Having backend deployed is great and all, but its usefulness is dubios without also having an accompanying frontend. Shouldn't be too hard in principle, but unclear what branch we should be deploying by default and whether it should be customizable.
The text was updated successfully, but these errors were encountered: