Repository navigation
Restore Assignment 1 SQL execution feedback alongside Assignment 2 - #492
Closed
danielrazavi wants to merge 1 commit into
Closed
danielrazavi wants to merge 1 commit into
danielrazavi wants to merge 1 commit into
Conversation
|
Thanks for your contribution! 🎉 Please remember to tag or request a review from the DSI team. Give us up to 72 hours to review your pull request. We appreciate your patience and efforts. |
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 changes are you trying to make?
Restore Assignment 1 SQL execution feedback alongside the existing Assignment 2 grader. October 9 commit
3fe0023c0af279b275f746948ad08134a631a25freplaced the old shared runner. This restores A1 in a separate workflow and runner, leaving all existing A2 files unchanged.assignment1.sqlfiles on student-owned repositories, onassignment-one/assignment-1and A2 branch aliases. Mixed A1/A2 submissions on A2 branches run both workflows independently.What did you learn from the changes?
The March 24–April 5 runner (
cf333a0,0349f73,3445382,f7e32c2,ae700d8) executed SQL and displayed results; it did not check correctness or award marks. Immediately before October 9, it was manual-only and prioritized A2 over A1 when both files changed. Restored feedback explicitly labels executable SQL as requiring instructor review.Was there another approach?
A separate A1 workflow avoids modifying the current A2 workflow, grading rules, regression tests, or report format. Shared-workflow routing would have required changing current A2 behavior.
Challenges and conflicts
No merge conflicts against
mainatcf65aa97590eba771031c052e08db3b62f5b5d8f. This is a new branch adding four files; no current files are overwritten.Automatic runs retain A2's student-repository owner restriction; upstream
UofT-DSIuse is manual. A2's existing branch restrictions are unchanged, so A2 does not automatically run from an A1 branch. GitHub token restrictions can prevent PR comments; manual runs with appropriate permissions are the fallback. The selected submission ref must include the restored runner/tests, and manual selection requires an unmergedassignment1.sqlchange against main.How were these changes tested?
A2_SOLUTION_RUBRIC, which was unavailable).git diff --checkpassed. Local tests used Python 3.9.6; workflow specifies Python 3.11. GitHub-hosted execution and actual PR comment delivery have not been exercised.Related task
Urgent Trello restoration task
See
.github/scripts/assignment1-feedback.mdfor provenance, usage, and limitations.Checklist