fix(ci): Improve Continuous Improvement Docs (#15373)

## todo:
- going to try to add more info because we removed some elements from
this page

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
Some information regarding continuous integration wasn't precise enough.
- I've added some more specificity regarding what we actually do in our
CI process
- We already mention the fast revert method in the Workflow page, so I
removed it from this page
- Moved the deployment block to the bottom, if we have more public info
I may move it to a different page

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Author: kenzoengineer

develop-docs/development-infrastructure/continuous-integration.mdx

@@ -1,27 +1,25 @@
 ---
 title: Continuous Integration
-description: Sentry uses a variety of continuous integration services to help ensure we don't accidentally break the application.
+description: Continuous Integration at Sentry validates code changes by running test suites, linters, and other checks to catch bugs and regressions before they reach production, maintaining a high bar for code quality and reliability. CI also builds deployable artifacts like container images, ensuring consistent and reproducible environments across local development and production.
 sidebar_order: 80
 ---
 
-## Deployments
-
-[GoCD](https://deploy.getsentry.net) is used for deployments. Please refer to the [internal user guide](https://www.notion.so/sentry/GoCD-User-Guide-4f8456d2477c458095c4aa0e67fc38a6).
-
 ## GitHub Actions
 
-GitHub actions is our primary CI system and runs our tests on every pull request and on merges to master. It is required that tests pass before changes can be merged.
+We use Github Actions as our primary CI system. With it, we run many quality checks, including but not limited to testing, linting, and code coverage. We only run front end tests if there are front end changes, and vice versa for back end tests. We also run acceptance tests to verify end-to-end functionality. These actions run in pull requests and also merges into the mainline. Pull requests must successfully run all actions in order to be merged into the mainline.
 
 ## Docker images
 
 We primarily use [a composite GitHub action](https://github.com/getsentry/action-build-and-push-images) for building and pushing images. This ensures that the workflows for building and publishing images are standardized, and appropriate metadata is available in the images. The standard for artifact management can be found [here](https://www.notion.so/sentry/Standard-Spec-Artifact-Management-22a8b10e4b5d80ecb6dcca3eb4558f5b).
 
+Our other shared composite actions are [documented internally](https://www.notion.so/sentry/Sentry-Composite-Actions-2ab8b10e4b5d80c6bc03fcd3079aed2a).
+
 We use GHCR (github container registry) for images that are used in CI, self-hosted, and local development. GAR (google artifact registry) is used for images that are used in prod.
 
-## Fast-Revert
-In order to facilitate quick changes to unblock failures on default branches, many of our repositories have a fast-revert workflow. In order to use it, PR's can be automatically reverted once a label `Trigger: Revert` is applied. More details found [here](https://www.notion.so/sentry/Standard-Spec-Fast-Revert-2388b10e4b5d8019bc98d863703d1b17?pvs=25)
+## CI workflow for testing changes with getsentry
 
+See [Workflow](/development/workflow/) for information on testing and reverting.
 
-## CI workflow for testing changes with getsentry
+## Deployments
 
-See [Workflow](/development/workflow/).
+At Sentry we use [GoCD](https://deploy.getsentry.net) for our deployments. Please refer to the [internal deployments documentation](https://www.notion.so/sentry/Deployments-GoCD-2d197a53f2464807962a503cd14d8973) for more information.