Update CLA URLcla-url

19 files changed, 38 insertions, 38 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2e32d5fa28..44de22c86c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,7 +12,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -50,7 +50,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/amqp10_common/CONTRIBUTING.md b/deps/amqp10_common/CONTRIBUTING.md
index 45bbcbe62e..339d097deb 100644
--- a/deps/amqp10_common/CONTRIBUTING.md
+++ b/deps/amqp10_common/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/amqp_client/CONTRIBUTING.md b/deps/amqp_client/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/amqp_client/CONTRIBUTING.md
+++ b/deps/amqp_client/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbit_common/CONTRIBUTING.md b/deps/rabbit_common/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbit_common/CONTRIBUTING.md
+++ b/deps/rabbit_common/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_amqp1_0/CONTRIBUTING.md b/deps/rabbitmq_amqp1_0/CONTRIBUTING.md
index 45bbcbe62e..339d097deb 100644
--- a/deps/rabbitmq_amqp1_0/CONTRIBUTING.md
+++ b/deps/rabbitmq_amqp1_0/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_codegen/CONTRIBUTING.md b/deps/rabbitmq_codegen/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_codegen/CONTRIBUTING.md
+++ b/deps/rabbitmq_codegen/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_jms_topic_exchange/CONTRIBUTING.md b/deps/rabbitmq_jms_topic_exchange/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_jms_topic_exchange/CONTRIBUTING.md
+++ b/deps/rabbitmq_jms_topic_exchange/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_management_agent/CONTRIBUTING.md b/deps/rabbitmq_management_agent/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_management_agent/CONTRIBUTING.md
+++ b/deps/rabbitmq_management_agent/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_random_exchange/CONTRIBUTING.md b/deps/rabbitmq_random_exchange/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_random_exchange/CONTRIBUTING.md
+++ b/deps/rabbitmq_random_exchange/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_recent_history_exchange/CONTRIBUTING.md b/deps/rabbitmq_recent_history_exchange/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_recent_history_exchange/CONTRIBUTING.md
+++ b/deps/rabbitmq_recent_history_exchange/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_sharding/CONTRIBUTING.md b/deps/rabbitmq_sharding/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_sharding/CONTRIBUTING.md
+++ b/deps/rabbitmq_sharding/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_stream/CONTRIBUTING.md b/deps/rabbitmq_stream/CONTRIBUTING.md
index 45bbcbe62e..339d097deb 100644
--- a/deps/rabbitmq_stream/CONTRIBUTING.md
+++ b/deps/rabbitmq_stream/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_stream_common/CONTRIBUTING.md b/deps/rabbitmq_stream_common/CONTRIBUTING.md
index 45bbcbe62e..339d097deb 100644
--- a/deps/rabbitmq_stream_common/CONTRIBUTING.md
+++ b/deps/rabbitmq_stream_common/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_stream_management/CONTRIBUTING.md b/deps/rabbitmq_stream_management/CONTRIBUTING.md
index 45bbcbe62e..339d097deb 100644
--- a/deps/rabbitmq_stream_management/CONTRIBUTING.md
+++ b/deps/rabbitmq_stream_management/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_top/CONTRIBUTING.md b/deps/rabbitmq_top/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_top/CONTRIBUTING.md
+++ b/deps/rabbitmq_top/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_trust_store/CONTRIBUTING.md b/deps/rabbitmq_trust_store/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_trust_store/CONTRIBUTING.md
+++ b/deps/rabbitmq_trust_store/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_web_dispatch/CONTRIBUTING.md b/deps/rabbitmq_web_dispatch/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_web_dispatch/CONTRIBUTING.md
+++ b/deps/rabbitmq_web_dispatch/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_web_mqtt_examples/CONTRIBUTING.md b/deps/rabbitmq_web_mqtt_examples/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_web_mqtt_examples/CONTRIBUTING.md
+++ b/deps/rabbitmq_web_mqtt_examples/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.
 
diff --git a/deps/rabbitmq_web_stomp/CONTRIBUTING.md b/deps/rabbitmq_web_stomp/CONTRIBUTING.md
index 23a92fef9c..9722e973fb 100644
--- a/deps/rabbitmq_web_stomp/CONTRIBUTING.md
+++ b/deps/rabbitmq_web_stomp/CONTRIBUTING.md
@@ -13,7 +13,7 @@ The process is fairly standard:
  * Create a branch with a descriptive name in the relevant repositories
  * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
  * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below)
+ * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
  * Be patient. We will get to your pull request eventually
 
 If what you are going to work on is a substantial change, please first ask the core team
@@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
 ## Contributor Agreement
 
 If you want to contribute a non-trivial change, please submit a signed copy of our
-[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time
+[Contributor Agreement](https://cla.pivotal.io/) around the time
 you submit your pull request. This will make it much easier (in some cases, possible)
 for the RabbitMQ team at Pivotal to merge your contribution.