You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dagger/dagger-hackathon/README.md
+13-16Lines changed: 13 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Welcome to the Dagger hackathon hosted by the [CNCF](https://community.cncf.io/cloud-native-calgary/) and [Code to Cloud](https://www.codetocloud.io/)! By the end of this hack, you will have a good understanding of how to use Dagger and the various use cases it can help support.
4
4
5
-
👀 Here’s the end-to-end flow:
5
+
**👀 Here’s the end-to-end flow:**
6
6
7
7

8
8
@@ -16,7 +16,7 @@ Welcome to the Dagger hackathon hosted by the [CNCF](https://community.cncf.io/c
16
16
17
17
5️⃣ Dagger agent inspects the issue using smart tools 🔍
18
18
19
-
6️⃣ A helpful comment appears on the PR 💬
19
+
6️⃣ A suggested code change appears on the PR 💬
20
20
21
21
## 🎯 Expected Outcomes
22
22
@@ -116,7 +116,7 @@ The below steps will take you through making a breaking change to a file in our
116
116
```
117
117
and confirm it fails
118
118
- Push the modified `addition.py` to your new feature branch
119
-
- In the GitHub UI, open a PR on the feature branch and compare to `main`
119
+
- In the GitHub UI, **open a PR** on the feature branch and compare to `main` (make sure to compare to `main` and not forked `main`)
120
120
121
121
---
122
122
@@ -125,21 +125,16 @@ The below steps will take you through making a breaking change to a file in our
> **Note:** The full API key will be provided during the hackathon.
141
-
142
-
- Put in your values and run in CLI:
137
+
- Fill in values for `github_branch`, `github_repo`, and `azure_openai_endpoint` (same as `OPENAI_BASE_URL`) and run in CLI:
143
138
```bash
144
139
dagger call \
145
140
--source="." \
@@ -192,8 +187,8 @@ Being able to navigate and explore logs in Dagger Cloud is a great skill to have
192
187
193
188
### ✅ Step 8: Trigger GitHub Action
194
189
195
-
- Delete the comment the Agent left on the PR in Step 6
196
-
-[Create GitHub secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) for everything in `.env` and name them `DAGGER_HACKATHON_GITHUB_TOKEN` and `OPENAI_API_KEY` for the GitHub token and Azure OpenAI API key respectively.
190
+
- Delete any comments the Agent left on the PR in Step 6
191
+
-[Create GitHub secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) for `DAGGER_CLOUD_TOKEN`, `DAGGER_HACKATHON_GITHUB_TOKEN` (what was `GITHUB_TOKEN`), and `OPENAI_API_KEY`.
197
192
- Make sure to update your GitHub Action to trigger on a pull request instead of a manual trigger.
198
193
199
194
Update the trigger from this:
@@ -211,7 +206,9 @@ on:
211
206
types: [opened, synchronize, reopened]
212
207
```
213
208
214
-
- Push your changes to Git and navigate back to your forked repo to see the GitHub Action running
209
+
- Push your changes to Git
210
+
211
+
- Now break the code in a different way in `addition.py` and push those changes. You should see a action running.
0 commit comments