docs: restore the teardown requirement in the README - #4
Merged
Conversation
The cohort README said teardown is 'part of the guidelines, not a separate graded file', contradicting the assignment chapter, the Deliverables list and the rubric, all of which require a teardown line in docs/portal_confirm.md. The scaffold already prompts for that line; only this prose was stale. Also moves the sample teardown date to August, matching the chapter. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
📝 HackYourFuture auto gradeAssignment Score: 40 / 100 ❌Status: ❌ Not passed Test Details |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What I built
Two small documentation fixes in the cohort hand-in repo.
How to review
README.md: the teardown paragraph and the step-3 table rowdocs/portal_confirm.md: sample date onlyThe cohort README said:
That contradicts three places that all require the opposite: assignment Task 3 step 4, the Deliverables list, and the rubric's Teardown dimension, which is worth 10 points and is graded on a final line in
docs/portal_confirm.md. The canonical repo already has the correct wording; only this mirror drifted. Thedocs/portal_confirm.mdscaffold already prompts for the line, so students following the scaffold were fine and students following the README were not.The sample teardown date also moves from May to August to match the chapter.
How to run
No code change, nothing to run. Diff is 5 added and 4 removed lines across two files.
What reviewers should see (expected results)
Deploy + what-if + portal evidence + teardown linedocs/portal_confirm.mdand explains why (the grader is static and cannot see Azure)HackYourFuture/data-assignment-week-14Self-check
docs/portal_confirm.mdscaffold already prompted for the teardown line.hyf/test.shor any workflow🤖 Generated with Claude Code