From 4197b7e9c4c844ab2b6a90b09e4867d57b28d692 Mon Sep 17 00:00:00 2001
From: Mandi Walls <mandi.walls@gmail.com>
Date: Tue, 14 Mar 2023 10:41:51 -0400
Subject: [PATCH] Removing CircleCI config and status indicator (#133)

---
 .circleci/config.yml | 69 --------------------------------------------
 README.md            |  3 +-
 2 files changed, 2 insertions(+), 70 deletions(-)
 delete mode 100644 .circleci/config.yml

diff --git a/.circleci/config.yml b/.circleci/config.yml
deleted file mode 100644
index a1d94ca..0000000
--- a/.circleci/config.yml
+++ /dev/null
@@ -1,69 +0,0 @@
-version: 2.1
-
-# The environment in which our build/deploy will run. Gives us a single place to define the image we use.
-executors:
-  build_env:
-    docker:
-      - image: cimg/python:3.9.2
-
-# Defines how to build the docs, and how to deploy them. We'll re-use these bits later.
-commands:
-  build_docs:
-    steps:
-      - checkout
-      - run:
-          name: Install Dependencies
-          command: |
-            pip3 install mkdocs pymdown-extensions pygments
-      - run:
-          name: Install Theme
-          command: |
-            git clone https://github.com/pagerduty/mkdocs-theme-pagerduty
-            cd mkdocs-theme-pagerduty && python3 setup.py install
-      - run:
-          name: Build Site
-          command: |
-            mkdocs build --clean
-
-  deploy_docs:
-    steps:
-      - run:
-          name: Install AWS CLI
-          command: |
-            pip3 install awscli
-      - run:
-          name: Deploy to S3
-          # Use --delete to remove any old files from bucket too, so we don't keep stale info around.
-          command: |
-            aws s3 sync site/ s3://$AWS_S3_BUCKET --acl public-read --cache-control "max-age=86400" --exclude "*.py*" --delete
-      - run:
-          name: Invalidate CloudFront Cache
-          command: |
-            aws configure set preview.cloudfront true
-            aws cloudfront create-invalidation --distribution-id $AWS_CF_DISTRIBUTION_ID --paths "/*"
-
-# We only have two jobs, one builds the docs, the other both builds and deploys them.
-jobs:
-  build:
-    executor: build_env
-    steps:
-      - build_docs
-
-  deploy:
-    executor: build_env
-    steps:
-      - build_docs
-      - deploy_docs
-
-# Just the one workflow. It always builds, buy only deploys when on the master branch.
-workflows:
-  version: 2
-  build-and-deploy:
-    jobs:
-      - build
-      - deploy:
-          requires:
-            - build
-          filters:
-            branches:
-              only: master
diff --git a/README.md b/README.md
index 48728cf..f45b9f0 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,6 @@
-# PagerDuty Incident Response Documentation [![Build Status](https://circleci.com/gh/PagerDuty/incident-response-docs/tree/master.svg?style=svg)](https://circleci.com/gh/PagerDuty/incident-response-docs)
+# PagerDuty Incident Response Documentation 
 [![Netlify Status](https://api.netlify.com/api/v1/badges/ca66d085-7d5f-4a57-81c7-4eb104c9bdb7/deploy-status)](https://app.netlify.com/sites/incident-response-docs/deploys)
+
 This is a public version of the Incident Response process used at PagerDuty. It is also used to prepare new employees for on-call responsibilities, and provides information not only on preparing for an incident, but also what to do during and after. See the [about page](docs/about.md) for more information on what this documentation is and why it exists.
 
 You can view the documentation [directly](docs/index.md) in this repository, or rendered as a website at https://response.pagerduty.com.