diff --git a/.github/workflows/lab1-smoke.yml b/.github/workflows/lab1-smoke.yml new file mode 100644 index 000000000..a7f7d745b --- /dev/null +++ b/.github/workflows/lab1-smoke.yml @@ -0,0 +1,36 @@ +name: Lab 1 juiceshop Smoke Test + +on: + pull_request: + branches: ["main"] + +permissions: + contents: read + +jobs: + smoke-test-juice-shop: + runs-on: ubuntu-latest + + services: + juice-shop: + image: bkimminich/juice-shop:v20.0.0 + ports: + - 3000:3000 + + steps: + - name: Wait for Juice Shop + run: | + for i in $(seq 1 30); do + if curl --silent --fail http://localhost:3000/rest/admin/application-version; then + echo "Juice Shop is ready" + exit 0 + fi + echo "Waiting for Juice Shop..." + sleep 2 + done + echo "Juice Shop did not start in time" + exit 1 + + - name: Verify homepage HTTP 200 + run: | + curl --silent --fail --head http://localhost:3000 \ No newline at end of file diff --git a/submissions/embeddings/l1_pr.png b/submissions/embeddings/l1_pr.png new file mode 100644 index 000000000..62a94cc7b Binary files /dev/null and b/submissions/embeddings/l1_pr.png differ diff --git a/submissions/lab1.md b/submissions/lab1.md index b0bacf73d..2d5e62779 100644 --- a/submissions/lab1.md +++ b/submissions/lab1.md @@ -99,7 +99,7 @@ Required checklist (the template must include all three items): - File: `.github/PULL_REQUEST_TEMPLATE.md` - Sections included: Goal / Changes / Testing / Artifacts / Checklist / Personal Notes - Checklist items: Title is clear (`feat(labN): `), No secrets/large temp files committed, `submissions/labN.md` exists -- Auto-fill verified: [x] Yes — PR description showed my template [pr](embeddings/l1_pr.png) +- Auto-fill verified: [x] Yes — PR description showed my template [pr](embeddings/l1_pr.png) or [pr on github](https://github.com/MikeNovikoff/DevSecOps-Intro-Mike/pull/2/commits/7cc7549e3a16558a963ae2dafb41d6c8b8dafc20) --- @@ -117,11 +117,6 @@ Required checklist (the template must include all three items): - TA: [@pierrepicaud](https://github.com/pierrepicaud) 4. **Follow** at least 3 classmates from the course -**Add to `submissions/lab1.md`:** - -A "GitHub Community" section with 1-2 sentences explaining: -- Why starring repositories matters in open source -- How following developers helps in team projects and professional growth
💡 GitHub Social Features @@ -138,6 +133,13 @@ A "GitHub Community" section with 1-2 sentences explaining: - Build professional connections beyond the classroom - Stay updated on classmates' work for future collaboration +## GitHub Community + +Starring repositories helps developers bookmark useful projects and shows support for maintainers. Popular repositories with many stars are often easier to discover and have stronger community engagement. + +Following developers helps me learn from their work, discover new projects, and stay informed about updates in technologies that interest me. It also makes collaboration easier in team environments and helps build a professional network. + +
---