From bbf10041d979c8dcef842ec3b2d26c7c7a111aea Mon Sep 17 00:00:00 2001
From: Mo King <muhsinking@gmail.com>
Date: Fri, 9 May 2025 09:05:22 -0400
Subject: [PATCH 1/2] Add build args section

---
 docs/serverless/workers/github-integration.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/serverless/workers/github-integration.md b/docs/serverless/workers/github-integration.md
index 658aa348..5033dacc 100644
--- a/docs/serverless/workers/github-integration.md
+++ b/docs/serverless/workers/github-integration.md
@@ -51,6 +51,10 @@ To deploy a worker from a GitHub repository:
 
 RunPod will build your Docker image and deploy it to your endpoint automatically. You'll be redirected to the endpoint details page when complete.
 
+## GitHub build arguments
+
+
+
 ## Monitoring build status
 
 You can monitor your build status in the **Builds** tab of your endpoint detail page. Builds progress through these statuses:

From 908cc30bd6d9a04df8fcc59143f886838664a839 Mon Sep 17 00:00:00 2001
From: Mo King <muhsinking@gmail.com>
Date: Fri, 9 May 2025 16:06:17 -0400
Subject: [PATCH 2/2] add github build args

---
 docs/serverless/workers/github-integration.md | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)

diff --git a/docs/serverless/workers/github-integration.md b/docs/serverless/workers/github-integration.md
index 5033dacc..aeefccc7 100644
--- a/docs/serverless/workers/github-integration.md
+++ b/docs/serverless/workers/github-integration.md
@@ -53,7 +53,55 @@ RunPod will build your Docker image and deploy it to your endpoint automatically
 
 ## GitHub build arguments
 
+When deploying a worker from a GitHub repo, you can use specify build arguments for your Dockerfile using `ARG`, allowing you to parameterize values in your Dockerfile instructions. Unlike environment variables, these variables do not persist into the final container, so they won't affect your handler function code.
 
+You can specify build arguments either in your Dockerfile, or using the RunPod UI.
+
+:::note
+
+For comprehensive information about using `ARG`, refer to the [official Docker documention](https://docs.docker.com/build/building/variables/).
+
+:::
+
+### Using build arguments in your Dockerfile
+
+To use build arguments in your Dockerfile, declare variables using the `ARG` keyword, then reference them using `$` syntax.
+
+For example:
+
+```dockerfile
+# Base image from RunPod's container registry
+ARG CUDA_VERSION=11.8.0
+ARG BASE_VERSION=0.6.3
+
+# Use build arguments to specify the base image version
+FROM runpod/base:${BASE_VERSION}-cuda${CUDA_VERSION}
+```
+
+You must declare an ARG in your Dockerfile before you can reference it, even if you've defined it in the RunPod UI.
+
+For example, you could declare variables using the UI
+
+### Setting build arguments in the RunPod UI
+
+To customize your build arguments without modifying your Dockerfile, you can specify them using the RunPod console.
+
+When [deploying a worker](#deploying-from-github) from GitHub:
+
+1. During the endpoint configuration process, find the **Build Args** section (below **Public Environment Variables**).
+2. Enter key-value pairs for your build arguments.
+3. These will be passed to your Docker build process.
+
+You must declare an `ARG` in your Dockerfile before you can reference it, even if you've defined it in the RunPod UI:
+
+```dockerfile
+# Build arguments defined in the UI must still be declared in your Dockerfile
+ARG CUDA_VERSION
+ARG BASE_VERSION
+
+# Use build arguments to specify the base image version
+FROM runpod/base:${BASE_VERSION}-cuda${CUDA_VERSION}
+```
 
 ## Monitoring build status