Skip to content

Commit a4da8df

Browse files
kdmccormickkaustavb12
authored andcommitted
docs: channel renamed to #pr-sandboxes
KYLE-1234
1 parent 7e070eb commit a4da8df

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

app/helpers/messages.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,4 +178,4 @@ def get_generic_error_summary() -> str:
178178
"""
179179
Generate summary for generic error during sandbox deployment
180180
"""
181-
return "\n\n### 🚫 Sandbox deployment failed due to an Internal Server Error. Please retry the deployment and if the issue persistes, please contact [#grove-pr-watcher](https://openedx.slack.com/archives/C05519HHZKM) slack channel."
181+
return "\n\n### 🚫 Sandbox deployment failed due to an Internal Server Error. Please retry the deployment and if the issue persistes, please contact [#pr-sandboxes](https://openedx.slack.com/archives/C05519HHZKM) slack channel."

docs/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -341,7 +341,7 @@ by the PR author. The source repo/branch of the PR is configured as a custom MFE
341341
point in time in the sandbox cluster. If this limit is reached, any new sandbox
342342
creation will fail with the message `Sandbox deployment has been cancelled since
343343
the maximum number of sandboxes are already deployed`. Please ping in the
344-
[#grove-pr-watcher](https://openedx.slack.com/archives/C05519HHZKM) Slack channel
344+
[#pr-sanboxes](https://openedx.slack.com/archives/C05519HHZKM) Slack channel
345345
in this case.
346346
2. The destroy sandbox pipeline sometimes fails due to the DigitalOcean's API
347347
related to MySQL being flaky and also due to Kubernetes namespace taking a long
@@ -350,7 +350,7 @@ where some sandbox resources are deleted and some are not. This is only an issue
350350
for PR authors if they are trying to [recreate a sandbox](#destroying-and-recreating-sandboxes).
351351
The "Generating Initial Sandbox Configs" step might fail in this case if the destroy
352352
pipeline had failed earlier. Please ping in the
353-
[#grove-pr-watcher](https://openedx.slack.com/archives/C05519HHZKM) Slack channel
353+
[#pr-sandboxes](https://openedx.slack.com/archives/C05519HHZKM) Slack channel
354354
in this case.
355355
3. The automation app posts a "Waiting for status of next steps" message between
356356
deployment steps. This message means that the last step was completed
@@ -367,5 +367,5 @@ by pushing a commit to your PR.
367367
> the list of known/reported [issues in Github](https://github.com/open-craft/pr-sandbox-automation/issues).
368368
> Please feel free to create a new issue there or add comments to an
369369
> existing issue, or, report the issue to
370-
> the [#grove-pr-watcher](https://openedx.slack.com/archives/C05519HHZKM)
370+
> the [#pr-sandboxes](https://openedx.slack.com/archives/C05519HHZKM)
371371
> Slack channel.

0 commit comments

Comments
 (0)