-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
🚧 automated staging server - master-1
#3089
Conversation
Important Auto Review SkippedDraft detected. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
86be02d
to
56fbad6
Compare
cadc6dc
to
3b80bf0
Compare
0c59089
to
af7f47a
Compare
233df2e
to
d5224a6
Compare
Master server on foundation-1, used as a template to create new staging servers.
This PR must be kept open so that Buildkite can refresh
staging-site-master-1
on new commits.See Github action
.github/workflows/sync-master.yml
that keeps it in sync withstaging-site-master
.