add more readmes

Author: sidpalas

01-history-and-motivation/README.md

@@ -0,0 +1,34 @@
+# 01. History and Motivation
+
+Continuous Integration (CI) has dramatically transformed the way we build, test, and deliver software. What once took weeks or months is now handled in minutes — all thanks to decades of innovation in tooling and process.
+
+## Speed of Software Delivery over Time
+
+The time between writing and shipping software has shrunk drastically over the decades:
+
+| Era             | Delivery Method               | Turnaround Time        |
+|------------------|-------------------------------|------------------------|
+| 🧮 1960s–70s      | **Punch cards / Mainframes**    | Days to weeks          |
+| 💾 1980s–90s      | **Floppy disks, CDs**          | Monthly to yearly      |
+| 🌐 2000s          | **Server deployments**         | Weekly to quarterly    |
+| ☁️ 2010s–Now      | **CI/CD pipelines & cloud**     | Multiple times per day |
+
+![](./readme-assets/speed-of-delivery-over-time.png)
+
+## History of CI Systems
+
+| Year | CI Tool           | Significance |
+|------|-------------------|--------------|
+| 1997 | **Tinderbox**     | Mozilla’s early build tracker – one of the first CI-like systems. |
+| 2001 | **CruiseControl** | First widely adopted open-source CI server. |
+| 2004 | **Hudson**        | Friendly UI and plugin support for Java CI; widely adopted. |
+| 2006 | **TeamCity**      | JetBrains' commercial CI with strong IDE and test integration. |
+| 2007 | **Bamboo**        | Atlassian's CI/CD tool with tight JIRA/Bitbucket integration. |
+| 2011 | **Jenkins**       | Community-driven fork of Hudson; became CI standard for years. |
+| 2011 | **Travis CI**     | First GitHub-native CI/CD as a service. |
+| 2011 | **CircleCI**      | Cloud CI/CD with fast feedback and Docker-native builds. |
+| 2015 | **GitLab CI/CD**  | Built-in CI/CD pipelines in GitLab, configured via YAML. |
+| 2016 | **AWS CodeBuild** | Managed CI inside AWS ecosystem. |
+| 2018 | **GitHub Actions**| GitHub-native automation with deep ecosystem and community support. |
+
+![](./readme-assets/ci-timeline.png)

01-history-and-motivation/readme-assets/ci-timeline.png

@@ -0,0 +1,13 @@
+# 02. Why GitHub Actions
+
+
+![](./readme-assets/developer-surveys.png)
+
+GitHub Actions is one of the most popular CI tools across the industry. Here is a comparison with some of the other top choices:
+
+| Tool        | Why Yes?                                                                                                                                             | Why No?                                                                                                                |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| GitHub Actions | • Your code is (likely) on GitHub already  <br> • Minimal barrier to entry <br> • Expansive public marketplace <br> • Market leadership leads to improved tooling (like [namespace.so](https://namespace.so)!) | • If you aren’t already using GitHub <br> • Less powerful pipeline reuse primitives <br> • Painful debugging experience <br> • Limited analytics/observability |
+| GitLab CI   | • Your code (might be) on GitLab already <br> • Minimal barrier to entry (if using GitLab) <br> • Deep integration with other GitLab features <br> • GitLab “Auto DevOps” | • If you aren’t already using GitLab <br> • Smaller public marketplace (<500 total)                                       |
+| CircleCI    | • Your code isn’t on GitHub or GitLab (CircleCI is VCS agnostic) <br> • Built-in “retry with SSH” feature is 🔥                                            | • Requires initial setup (vs. GHA + GitLab) <br> • Smaller public orbs marketplace (3653 total)                           |
+| Jenkins     | • You (might) already be using it <br> • The plugin ecosystem is vast                                                                                      | • Incurs significant maintenance overhead (security and plugin dependencies) <br> • Groovy pipeline DSL feels outdated    |

01-history-and-motivation/readme-assets/speed-of-delivery-over-time.png

@@ -0,0 +1,55 @@
+# 05. Marketplace Actions
+
+The [GitHub Actions Marketplace](https://github.com/marketplace?type=actions) is one of the platforms best features. There are thousands of open source actions you can use to build your automation pipelines.
+
+
+![](./readme-assets/gha-marketplace.png)
+
+## Assessing Actions
+
+Not all actions are created equal. You should review before use.
+
+1. Assess like any open source dependency
+2. Does it do what you need it to?
+3. Signals for quality/trustworthiness:
+    - User verification
+    - Number of stars
+    - Active commit history
+
+## Security
+
+Actions often run with access to sensitive data/environments
+
+The only way to ensure you are running the same version is to pin with the commit hash:
+```
+❌ - uses: actions/checkout
+❌ - uses: actions/checkout@v4
+❌ - uses: actions/checkout@v4.2.2
+✅ - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+```
+
+In 2025, a supply chain attack affected many repositories who did not follow this approach: https://www.wiz.io/blog/github-action-tj-actions-changed-files-supply-chain-attack-cve-2025-30066
+
+## Popular Actions
+
+### Official Actions (from GitHub)
+- checkout https://github.com/marketplace/actions/checkout-action 
+- cache https://github.com/marketplace/actions/cache 
+- artifact
+  - upload https://github.com/marketplace/actions/upload-a-build-artifact
+  - download https://github.com/marketplace/actions/download-a-build-artifact
+- github-script https://github.com/marketplace/actions/github-script
+
+### Install Runtimes / Dependencies (e.g. node)
+- setup-node https://github.com/marketplace/actions/setup-node-js-environment
+- setup-go https://github.com/marketplace/actions/setup-go-environment
+- setup-java-jdk https://github.com/marketplace/actions/setup-java-jdk
+
+### Auth to 3rd External Application / Platform
+- AWS https://github.com/marketplace/actions/configure-aws-credentials-action-for-github-actions
+- Azure https://github.com/marketplace/actions/azure-login
+- GCP https://github.com/marketplace/actions/authenticate-to-google-cloud
+
+### Other
+- Super-linter https://github.com/marketplace/actions/super-linter
+- Build / push container images: https://github.com/marketplace/actions/build-and-push-docker-images