You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, a fork won’t work because you can’t make forks of public repositories private. However, GitHub offers an “import” feature, which does support private repositories, for transferring code from one repository to another. Perhaps you or someone else could modify the instructions to mention that as an option instead of cloning the source repository directly.
That said, being able to configure multiple remotes in Git is an important skill. Currently, the exam effectively tests that skill, but implementing this suggestion would undermine that, which might be undesirable. On the other hand, the auto-grader can’t itself check which method the student used, so adding instructions for the “import” feature would merely make explicit something that students can already do.
Remotes are useful, particularly when you are working with a group like RCOS which may want to work together outside of the normal development path for the project ... I.e. perhaps the Open Horizons team at RPI would want to work out of a common fork outside of IBM and then make PRs from this common fork into the main fork of Open Horizon. I think learning remotes are useful, but the description needs to be better explained.
No description provided.
The text was updated successfully, but these errors were encountered: