My apologies. I was wrong. Clearly you can raise issues on a forked version.
However! When you push your local changes up to the forked version (in this case, the one in foundersandcoders), it automatically sets the "base" for the PR as the original repo (in this case, the one in your profile).
This is confusing for students. Especially while they are new to git. But even experienced people are liable to forget or not notice this. It causes confusion in the classroom. This is not something that I am guessing might happen. It is a pattern that I have observed over the past cohort, which has repeated itself. I am attempting to stop us from repeating mistakes that we already know about.
My apologies. I was wrong. Clearly you can raise issues on a forked version.
However! When you push your local changes up to the forked version (in this case, the one in
foundersandcoders), it automatically sets the "base" for the PR as the original repo (in this case, the one in your profile).This is confusing for students. Especially while they are new to git. But even experienced people are liable to forget or not notice this. It causes confusion in the classroom. This is not something that I am guessing might happen. It is a pattern that I have observed over the past cohort, which has repeated itself. I am attempting to stop us from repeating mistakes that we already know about.
relates #1