From 4e00ac28852a63cadeab944cb8470e8dc23d8e47 Mon Sep 17 00:00:00 2001 From: Harald Hamrin Reinhed Date: Thu, 28 Aug 2025 10:18:09 +0200 Subject: [PATCH] added file --- .../demo/week2/haraldhr-lflod/README.md | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 contributions/demo/week2/haraldhr-lflod/README.md diff --git a/contributions/demo/week2/haraldhr-lflod/README.md b/contributions/demo/week2/haraldhr-lflod/README.md new file mode 100644 index 0000000000..953a0abb41 --- /dev/null +++ b/contributions/demo/week2/haraldhr-lflod/README.md @@ -0,0 +1,34 @@ +# Assignment Proposal + +## Title + +Setting up a CI pipeline with GitHub Webhooks and REST API feedback + +## Names and KTH ID + +- Harald Hamrin Reinhed (haraldhr@kth.se) +- Ludwig Flod (lflod@kth.se) + +## Deadline + +- Week 2 + +## Category + +- Demo + +## Description + +The demo will show how to implement a simple Continuous Integration (CI) workflow from scratch using GitHub webhooks and the GitHub REST API. +The workflow will cover the following steps: +1. Setting up a GitHub webhook that triggers on new commits or pull requests. +2. Implementing a lightweight server that listens for webhook events. +3. Running automated build and test commands on the triggered event. +4. Reporting the results of the build back to GitHub by updating the commit status or posting a comment through the REST API. + +The demo will be performed live by pushing both failing and successful commits to show the feedback loop in action. +The idea is to give a general idea of how to implement it, so some functions will be pre-written. + +**Relevance** + +This proposal is directly relevant to CI, as it demonstrates the fundamentals of Continuous Integration: automatic builds, testing, and feedback triggered by version control events. The example makes visible how CI tools GitHub Actions work under the hood, and highlights the importance of automation, integration, and rapid feedback in modern software development workflows.