-
Notifications
You must be signed in to change notification settings - Fork 2
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: deploy chronicles to radix #529
Conversation
|
I suggest following the repository-convention of releasing: pushing to prod when we merge the release PR.
@tormodAase, @Jonas-Omdal what do you think? |
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 fresh 馃憣
I think we should discuss how we want to release as you mentioned. Made a comment in the PR for it.
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.
LGTM!
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 hella nice 馃憣 馃敟
Added deploy setup for hosting Chronicles Web in Radix:
https://web-chronicles-test.radix.equinor.com/
https://web-chronicles-prod.radix.equinor.com/
Currently using tags to push build requests to radix, feel free to add your own suggestions and opinions on how we should schedule releases to test and production 馃憤
EDIT: Added release to production in the publish:all script and configured Radix to deploy to test from main