Skip to content

Commit 355cbc6

Browse files
fixing indentation
1 parent 9888f63 commit 355cbc6

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

examples/codex/codex-cicd.ipynb

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"\n",
1212
"This cookbook shows you how to embed the OpenAI Codex CLI into your CI/CD pipeline so that when your builds or tests fail, codex automatically generates & proposes fixes. The following is an example in a node project with CI running in GitHub Actions. \n",
1313
"\n",
14-
"## Workflow Diagram\n",
14+
"## End to End Flow\n",
1515
"\n",
1616
"Below is the pipeline flow we’ll implement:\n",
1717
"\n",
@@ -152,7 +152,11 @@
152152
"id": "8148024b",
153153
"metadata": {},
154154
"source": [
155+
"## Step 4: Actions Workflow kicked off\n",
156+
"\n",
155157
"You can navigate to the Actions tab under Repo to view the failing jobs in your Actions workflow. \n",
158+
"\n",
159+
"\n",
156160
"![](images/failing-workflow.png)\n"
157161
]
158162
},
@@ -162,14 +166,18 @@
162166
"metadata": {},
163167
"source": [
164168
"The Codex workflow should be triggered upon completiton of the failed workflow. \n",
165-
"![](images/codex-workflow.png)"
169+
"\n",
170+
"\n",
171+
"![](images/codex-workflow.png)\n",
172+
"\n"
166173
]
167174
},
168175
{
169176
"cell_type": "markdown",
170177
"id": "d08a3ecc",
171178
"metadata": {},
172179
"source": [
180+
"## Step 5: Codex generated PR for review\n",
173181
"And after the Codex workflow completes execution, it should open a pull request from the feature branch codex/auto-fix. Check to see if everything looks good and then merge it.\n",
174182
"\n",
175183
"![](images/codex-pr.png)"

0 commit comments

Comments
 (0)