diff --git a/README.md b/README.md
index a05a3ad341..37e049d205 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,6 @@
 | **GHA CI**           | [![gha ci][gha-ci-img]][gha-ci-url]           |
 | **Buildkite CI**     | [![buildkite ci][buildkite-ci-img]][buildkite-ci-url] |
 | **Code Coverage**    | [![codecov][codecov-img]][codecov-url]        |
-| **Bors enabled**     | [![bors][bors-img]][bors-url]                 |
 | **DOI**              | [![zenodo][zenodo-img]][zenodo-url]           |
 
 [docs-bld-img]: https://github.com/CliMA/ClimaCore.jl/workflows/Documentation/badge.svg
@@ -25,9 +24,6 @@
 [codecov-img]: https://codecov.io/gh/CliMA/ClimaCore.jl/branch/main/graph/badge.svg
 [codecov-url]: https://codecov.io/gh/CliMA/ClimaCore.jl
 
-[bors-img]: https://bors.tech/images/badge_small.svg
-[bors-url]: https://app.bors.tech/repositories/32973
-
 [zenodo-img]: https://zenodo.org/badge/356355994.svg
 [zenodo-url]: https://zenodo.org/badge/latestdoi/356355994
 
diff --git a/bors.toml b/bors.toml
deleted file mode 100644
index e47c0ddfad..0000000000
--- a/bors.toml
+++ /dev/null
@@ -1,16 +0,0 @@
-status = [
-  "test-os (ubuntu-20.04)",
-  "test-os (windows-latest)",
-  # "test-os (macos-latest)",
-  "lib-climacore-vtk",
-  "lib-climacore-makie",
-  "lib-climacore-plots",
-  "lib-climacore-tempestremap",
-  "buildkite/climacore-ci",
-  "format",
-  "docbuild"
-]
-delete_merged_branches = true
-timeout_sec = 12600
-block_labels = [ "do-not-merge-yet" ]
-cut_body_after = "<!--"
diff --git a/docs/src/Contributing.md b/docs/src/Contributing.md
index e51f3c9c54..89a329a4f2 100644
--- a/docs/src/Contributing.md
+++ b/docs/src/Contributing.md
@@ -172,14 +172,6 @@ Depending on the content changed in the PR, some CI checks that
 are not necessary will be skipped.  For example doc only changes
 do not require the unit tests to be run.
 
-### The merge process
-
-We use [`bors`](https://bors.tech/) to manage merging PR's in the the `ClimaCore.jl` repo.
-If you're a collaborator and have the necessary permissions, you can type
-`bors try` in a comment on a PR to have integration test suite run on that
-PR, or `bors r+` to try and merge the code.  Bors ensures that all integration tests
-for a given PR always pass before merging into `master`.
-
 ### Integration testing
 
 Currently a number of checks are run during integration testing before being