diff --git a/serverless/workers/github-integration.mdx b/serverless/workers/github-integration.mdx
index 54bd0217..f89c2780 100644
--- a/serverless/workers/github-integration.mdx
+++ b/serverless/workers/github-integration.mdx
@@ -88,12 +88,63 @@ You can monitor your build status in the **Builds** tab of your endpoint detail
 | Completed | Runpod completed the build and upload.              |
 | Failed    | Something went wrong (check build logs).            |
 
+
 ## Updating your endpoint
 
 When you make changes to your GitHub repository, they won't automatically be pushed to your endpoint. To trigger an update for the workers on your endpoint, create a new release for the GitHub repository.
 
 For detailed instructions on creating releases, see the [GitHub documentation](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository).
 
+## Roll back to a previous build
+
+<Note>
+
+GitHub rollbacks are currently in beta. [Join our Discord](https://discord.gg/runpod) if you'd like to provide feedback.
+
+</Note>
+
+Roll back your endpoint to any previous build directly from the Runpod console. This restores your endpoint to an earlier version without waiting for a new GitHub release.
+
+### Requirements
+
+To roll back an endpoint, you need:
+
+- An existing endpoint deployed with GitHub integration.
+- At least one previous build available in your deployment history.
+
+### Roll back a deployment
+
+To roll back your endpoint to a previous build:
+
+<Steps>
+<Step title="Navigate to your endpoint">
+Open the endpoint details page in the [Serverless section](https://www.console.runpod.io/serverless) of the Runpod console.
+</Step>
+
+<Step title="Select a previous build">
+Click the **Builds** tab to view your deployment history.
+
+Find the build you want to roll back to, then click the three dots menu button next to that build.
+</Step>
+
+<Step title="Initiate the rollback">
+Select **Rollback** from the menu.
+
+Review the confirmation modal and click **Confirm** to proceed with the rollback.
+</Step>
+</Steps>
+
+After confirming, your endpoint rolls back to the selected build. A banner appears at the top of the endpoint page indicating the endpoint is on a rolled-back version.
+
+### Understanding rollback behavior
+
+When you roll back an endpoint:
+
+- Your endpoint immediately switches to the Docker image from the selected previous build.
+- The rollback banner displays at the top of your endpoint page to indicate the current state.
+- Your endpoint remains on the rolled-back version until you deploy a new release from GitHub.
+- When you push a new commit and create a release, the new build automatically becomes the active version and supersedes the rollback.
+
 ## Managing multiple environments
 
 GitHub integration enables streamlined development workflows by supporting multiple environments: