Implement hands on hp-push-tags

[dingZvel]

Exercise Review

Exercise Discussion

#94

Checklist

• If you require a new remote repository on the Git-Mastery organization, have you created a request for it?
• Have you written unit tests using repo-smith to validate the exercise grading scheme?
• Have you tested the download script using test-download.sh?
• Have you verified that this exercise does not already exist or is not currently in review?
• Did you introduce a new grading mechanism that should belong to git-autograder?
• Did you introduce a new dependency that should belong to app?

[dingZvel]

I'm not sure what to do when there's a conflict in repo names, i.e., the user already has a repo named samplerepo-preferences. We could ask the user for a new name to rename the fork (using gh repo fork --fork-name).
The gh fork command automatically creates the fork with the name samplerepo-preferences-1 if there's a conflict, and for now I just leave the repo name as is.

[damithc]

I'm not sure what to do when there's a conflict in repo names, i.e., the user already has a repo named samplerepo-preferences. We could ask the user for a new name to rename the fork (using gh repo fork --fork-name).
The gh fork command automatically creates the fork with the name samplerepo-preferences-1 if there's a conflict, and for now I just leave the repo name as is.

We can use an alternative fork name such as samplerepo-preferences-1 but in that case we should inform the user about it.
On a related note, GitHub does not allow us to fork the same repo twice. If the user already has a fork of this repo, we may have to abort the operation and inform the user about the conflict e.g., ask the user to delete the fork and run the download operation again.

[dingZvel]

We can use an alternative fork name such as samplerepo-preferences-1 but in that case we should inform the user about it. On a related note, GitHub does not allow us to fork the same repo twice. If the user already has a fork of this repo, we may have to abort the operation and inform the user about the conflict e.g., ask the user to delete the fork and run the download operation again.

Sure! Maybe I can submit follow-up commits regarding this later.

[dingZvel]

The follow-up commits are up!
Now it aborts the operation when the user already has a fork, and warns the user when there's a conflict in repo name.

[woojiahao]

This is pending some comments from @damithc on the original hands-on discussion. Let's come back to this once he confirms if we need to fork the repository.

[woojiahao]

Suggested change

pass

[woojiahao]

I left a comment for @damithc in the original hands-on discussion, but I doubt we actually need to fork the repository for the student. This would avoid polluting the student's Github with excessive repositories they might not be using