I never did PR to myself, always pushing directly into the repository. I can see how it can be useful in a course though.
All done. However, I cannot @mention or add Chris as a reviewer as he is not a collaborator on my repo.
Here’s my pull request. To @mozzadrella and @ccannon94, I think this exercise is somewhat confusing as it is now so It would be great if you can clarify it on the two points below for future students:
A push to remote master branch is required before pushing new branch with questions, otherwise only one (new branch) is created on the remote and so no pull request is possible as there is only one branch. This is obvious after doing the exercises but not for someone new to pull requests.
The assignment currently asks to just create a repo on GitHub, which most people interpret as personal GitHub, and in that case Chris cannot be assigned as a reviewer as asked because he is not a collaborator on the project (that’s my guess at least to why). There seems to be tons of screenshots where he is not a reviewer because of that, and the ones where he is are all created within Campus-Advisors organization, which is not what the assignment asks.
Anyway, this is minor of course, but I ended up spending way more time on this assignment than necessary so hopefully these comments are helpful for others. Thank you for making Campus Advisors possible, I am really enjoying it so far.
Thanks for that feedback @irinagain! We’re reworking this flow for the next version of the training.
- So if merge conflicts arise, git will ask for a human to decide which pieces of code, or if all of the code, should be kept. This is covered in depth later on, so I imagine your question was answered later in this module.