Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git solo #27

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Git solo #27

wants to merge 6 commits into from

Conversation

ar0r
Copy link
Collaborator

@ar0r ar0r commented Apr 19, 2024

Replaces the original git basics tutorial with a new version that starts with a local-only repository and introduces a remote repository only after students have learned the basics of creating commits. This request includes the required distribution files.

@borjasotomayor
Copy link
Member

I have pushed a number of updates to the tutorial in c1e51b8. We will eventually need to update screenshots to use the naming convention in the Student Resource Guide but, in the interim, we could get away with a warning box that says the screenshots use "solo" instead of "basics", and that they should ignore that discrepancy.

I also wonder whether it makes sense to spin off everything starting at "Working with a Remote Server" into an "Intermediate Git Tutorial". As it stands, the "Git Basics" tutorial feels very long.

One minor issue I wasn't sure how to address:

If you want your output to match ours, use the message "More salutations".

This "More salutations" isn't mentioned again in the tutorial, and presumably refers to some output the reader would compare their output with. Is this leftover from the CS 141 tutorial?

@ar0r
Copy link
Collaborator Author

ar0r commented May 24, 2024

I have updated the tutorial to address all the comments I received from James, except the suggestion to switch to setting the global default branch name to main. We can make this change once Techstaff updates the Linux machines.

I also addressed Borja's comments.

I think someone who is good at proofreading needs to do a careful proofreading pass.

My reading of the branches tutorial is that the students can use the repo they created for the basic sections of the tutorial or they can create a new one. I don't think we need to add any extra files to the basic distribution. Someone should verify this claim.

At some point, we may want to update the branches section to use Python examples rather than C for the sake of consistency. This change is not essential and should not hold up releasing this version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants