Replace Airflow Slack Invite old link to short link (#11071)

Follow up to apache/airflow#10034 https://apache-airflow-slack.herokuapp.com/ to https://s.apache.org/airflow-slack/ GitOrigin-RevId: e3a590075ec14a448b24be92f588793813355106
GoogleCloudPlatform · Jun 3, 2022 · 2e531c3 · 2e531c3
1 parent fc148d3
commit 2e531c3
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/.github/boring-cyborg.yml b/.github/boring-cyborg.yml
@@ -221,7 +221,7 @@ firstPRWelcomeComment: >
 
   Mailing List: [email protected]
 
-  Slack: https://apache-airflow-slack.herokuapp.com/
+  Slack: https://s.apache.org/airflow-slack/
 
 # Comment to be posted to congratulate user on their first merged PR
 firstPRMergeComment: >

diff --git a/BREEZE.rst b/BREEZE.rst
@@ -308,7 +308,7 @@ In case the problems are not solved, you can set the VERBOSE_COMMANDS variable t
 
 
 Then run the failed command, copy-and-paste the output from your terminal to the
-`Airflow Slack <https://apache-airflow-slack.herokuapp.com/>`_  #airflow-breeze channel and
+`Airflow Slack <https://s.apache.org/airflow-slack/>`_  #airflow-breeze channel and
 describe your problem.
 
 Other uses of the Airflow Breeze environment

diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
@@ -175,7 +175,7 @@ In general, your contribution includes the following stages:
    If you want to add more changes in the future, set up your fork and enable GitHub Actions.
 
 3. Join `devlist <https://lists.apache.org/[email protected]>`__
-   and set up a `Slack account <https://apache-airflow-slack.herokuapp.com>`__.
+   and set up a `Slack account <https://s.apache.org/airflow-slack>`__.
 
 4. Make the change and create a `Pull Request from your fork <https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork>`__.
 
@@ -1080,7 +1080,7 @@ You can join the channels via links at the `Airflow Community page <https://airf
 **IMPORTANT**
 We don't create new issues on JIRA anymore. The reason we still look at JIRA issues is that there are valuable tickets inside of it. However, each new PR should be created on `GitHub issues <https://github.com/apache/airflow/issues>`_ as stated in `Contribution Workflow Example <https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example>`_
 
-* The `Apache Airflow Slack <https://apache-airflow-slack.herokuapp.com/>`_ for:
+* The `Apache Airflow Slack <https://s.apache.org/airflow-slack/>`_ for:
    * ad-hoc questions related to development (#development channel)
    * asking for review (#development channel)
    * asking for help with PRs (#how-to-pr channel)

diff --git a/docs/build_docs.py b/docs/build_docs.py
@@ -745,7 +745,7 @@ def print_build_errors_and_exit(message) -> None:
 CHANNEL_INVITATION = """\
 If you need help, write to #documentation channel on Airflow's Slack.
 Channel link: https://apache-airflow.slack.com/archives/CJ1LVREHX
-Invitation link: https://apache-airflow-slack.herokuapp.com/\
+Invitation link: https://s.apache.org/airflow-slack/\
 """
 
 print_build_errors_and_exit("The documentation has errors. Fix them to build documentation.")

diff --git a/docs/project.rst b/docs/project.rst
@@ -86,7 +86,7 @@ Resources & links
   * Airflow users mailing list: [email protected]
 
 * `Issues on GitHub <https://github.com/apache/airflow/issues>`_
-* `Slack (chat) Channel <https://apache-airflow-slack.herokuapp.com/>`_
+* `Slack (chat) Channel <https://s.apache.org/airflow-slack/>`_
 * `More resources and links to Airflow related content on the Wiki <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Links>`_