Skip to content

Commit 701ce4f

Browse files
committed
added image run cdn script
1 parent d245a90 commit 701ce4f

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

data/posts/building-a-zero-dependency-event-driven-github-profile-updater-with-actions-and-webhooks.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,8 @@ jobs:
113113
114114
**Engineer's Note:** Notice the `-f -i -s` flags on the `curl` command. By default, `curl` will return a green success checkmark as long as it connects to the server, even if GitHub rejects your token with a `403 Forbidden`. Adding `-f` forces the pipeline to fail loudly if the API rejects the request, which saves hours of debugging.
115115

116+
![First test run but no update](https://cdn.jsdelivr.net/gh/ullaskunder3/blog-api@main/data/img/action-profile-update/first-test-did-run-but-no-update.png)
117+
116118
## Step 3: The Receiver (The Python Automation)
117119

118120
Over in my profile repository, I needed a script to catch the `blog_published` event, read my RSS feed, and rewrite the README.md.
@@ -219,6 +221,8 @@ jobs:
219221

220222
## The Result
221223

224+
![Final execution success](https://cdn.jsdelivr.net/gh/ullaskunder3/blog-api@main/data/img/action-profile-update/last-test-success.png)
225+
222226
The final execution time? **Under 15 seconds.** The compute cost? Practically zero. It only runs exactly when a new blog is pushed, using Python's ultra-fast standard library, making a single tiny HTTP request.
223227

224228
By avoiding black-box templates and writing the glue code myself, I ended up with a system that is perfectly tailored, completely secure, and infinitely easier to debug.

0 commit comments

Comments
 (0)