We are currently using the student login page across the entire application - instead, we want to use the student login page for the student routes, and the provider login page for everything else (go figure).
Right now, we don't need to use a ProtectedRoute, but eventually this will also need to be added.
We are currently using the student login page across the entire application - instead, we want to use the student login page for the student routes, and the provider login page for everything else (go figure).
Right now, we don't need to use a `ProtectedRoute`, but eventually this will also need to be added.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We are currently using the student login page across the entire application - instead, we want to use the student login page for the student routes, and the provider login page for everything else (go figure).
Right now, we don't need to use a
ProtectedRoute, but eventually this will also need to be added.I started working on this in the complete wrong branch, so I've linked the corresponding PR here.