Skip to content

Fix dead instructions link, align task numbers to the chapter, scope az login to HYF tenant#2

Merged
lassebenni merged 1 commit into
mainfrom
fix/instructions-link-and-task-numbers
Jun 1, 2026
Merged

Fix dead instructions link, align task numbers to the chapter, scope az login to HYF tenant#2
lassebenni merged 1 commit into
mainfrom
fix/instructions-link-and-task-numbers

Conversation

@lassebenni

Copy link
Copy Markdown
Collaborator

Three fixes surfaced while verifying the Week 5 ACR flow end-to-end.

1. Dead instructions link (the notable one)

The README sent students to hackyourfuture.github.io/datatrack/week-5/assignment for the full Task 7 (ACR push) steps — that URL 404s. Repointed to the Week 5 assignment page in the Notion curriculum.

2. Task numbers were off by one vs the chapter

The repo numbered tasks 1–7 (ACR push = Task 6), but the assignment chapter has 8 tasks (ACR push = Task 7, AI report = Task 8). A student reading both got conflicting numbers. Renumbered to match: added Task 3 for the provided test suite, so Dockerfile=4, Configuration=5, CI=6, ACR=7, AI=8. Updated README, ci.yml, Dockerfile, AI_ASSIST.md, src/pipeline.py, and the grader's deliverable message. Grader scoring tiers ("Level N") and logic are unchanged.

3. az login could land on the wrong tenant

README said az login --use-device-code with no tenant. Students who also have a personal/other-org Azure account would authenticate there and get unauthorized on az acr login. Now targets the HYF tenant: az login --use-device-code --tenant 07a14c4e-....

Verified: grader bash -n clean; no task-number references remain inconsistent; no github.io link remains.

🤖 Generated with Claude Code

… scope az login to HYF tenant

- README: the "full assignment instructions" link pointed at
  hackyourfuture.github.io/datatrack/week-5/assignment, which 404s. Repoint it
  to the Week 5 assignment page in the Notion curriculum.
- Renumber tasks to match the assignment chapter (8 tasks): add Task 3 (the
  provided test suite), so Dockerfile=4, Configuration=5, CI=6, ACR push=7,
  AI report=8. Updates README, ci.yml, Dockerfile, AI_ASSIST.md, pipeline.py,
  and the grader's deliverable message.
- README: az login now targets the HackYourFuture tenant
  (--tenant 07a14c4e-...), preventing the "wrong tenant" failure for students
  who also have a personal/other-org Azure account.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@lassebenni lassebenni left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Local review by Claude — 0 blocking, 0 warnings.

Python/bash assignment repo, so the dbt/PBI validators are N/A. Ran the applicable ones:

  • python -m py_compile src/pipeline.py tests/test_pipeline.py → OK
  • Grader bash -n .hyf/test.sh → OK, and ran it end-to-end on the scaffold: Score 39/100, pass=false (expected — NotImplementedError stubs still present). Logic intact; the edited deliverable message now reads Task 7 deliverable.
  • ci.yml change is a comment only; grade-assignment.yml untouched (no functional YAML change).
  • Task-number references are consistent across all 6 files (1→8 model); no github.io link or conflict markers remain.

Manual eyeball (not machine-verifiable): the new instructions link is a Notion page URL — it follows the curriculum's link convention and replaces a confirmed 404, but I can't confirm it resolves for a logged-in student from here. Worth a quick click-test before merge.

✅ No code issues to fix.

@lassebenni

Copy link
Copy Markdown
Collaborator Author

@copilot review

Copilot AI commented Jun 1, 2026

Copy link
Copy Markdown

@copilot review

Reviewed. I re-ran local checks (python -m py_compile, bash -n .hyf/test.sh, and ./.hyf/test.sh) and verified the branch is clean with no additional changes needed for this PR update.

@lassebenni lassebenni merged commit d180628 into main Jun 1, 2026
2 checks passed
@lassebenni lassebenni deleted the fix/instructions-link-and-task-numbers branch June 1, 2026 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants