This repository was archived by the owner on Sep 1, 2022. It is now read-only.
Test unhappy path #5
Description
Testing unhappy path
Before publishing, we need to test and account for the following "unhappy paths", the paths that users may take, and we want to steer them back onto the right course.
- Step 1: If user closes issue First draft edits #1 instead of Draft edits #2, then we should probably reopen it for them, link again to Draft edits #2, and/or show where the reference is that the missed
- "Welcome to the course! We're going to walk through some strategies for dealing with large repositories. This is a similar issue to First draft edits #1, but I'll let you decide if we should keep it or not."
- At the end, include a note about refreshing
- Should set protected branches on pull request add navigation and then remove them after the commit with "tricks" happens
- If the user makes a commit that doesn't fix "tricks" we should reiterate the instructions