Git Walkthrough #1

Follow along as Nancy & Marissa walk step-by-step through the process of adding a blog post to the Cleveland PyLadies website.
Setup notes: You will need a GitHub account, a text editor (we used VS Code), and a terminal window (Windows users need their Command Line and a Git terminal) for this walk-through. Make sure you are signed into GitHub, and then...
1) Open https://www.github.com/clepyladies/pyladies-official/ in a web browser
2) Click the "Fork" button in the top right to make a copy of the repository to your account. (See timestamp 6:18)
3) Clone your fork of the repository with your command line. We want to use the HTTPS version for this. (See timestamps 8:00 for what link to copy and 12:25 for the "git clone" command)
4) You should now have a directory called "pyladies-official" on your computer. Open this directory from your text editor. (See timestamp 20:10)
5) Make changes to the website from your text editor. (See timestamp 25:00 to see the change we made)
6) SAVE! We're almost done, but remember to save your changes before the next step.
7) From your terminal (or Git terminal, for Windows users), "git add" each file you modified or added. (See timestamp 31:15)
8) In that same terminal, arrow up a few times until you see "git status" again. This saves you
Read her post at https://clepyladies.github.io/pyladies-official/new-adventure/ (See timestamp 32:42)
9) The file you added should now be green, so "git commit -m" that change, along with a brief message. (See timestamp 32:55)
10) Once you've committed the change, you can "git push origin master" to sync your local changes up to your GitHub repository. (See timestamp 34:52) Note: we ran into an issue at this stage and used the GitHub browser method (at timestamp 39:25) to finish our change, so there is a non-terminal way to make changes to your GitHub repo.
11) Now that your local changes are synced to your fork of the pyladies-official repo, we're going to make a Pull Request. Go back to https://www.github.com/clepyladies/pyladies-official and open the Pull Requests tab (46:50).
12) Click "New Pull Request" (47:45)
13) Compare across forks, with your fork as the "head." (48:30)
14) If you see a green check mark that says "Able to merge," you can go ahead and click "Create pull request" (48:55) and leave a comment describing the changes you would like to merge. (49:05)
15) Click the green "Create pull request" button below your comment box to submit your pull request (50:00) & you're done! For now.
16) Whether the maintainer requests changes or merges your changes as they are, you've officially made your first Pull Request. That's a big deal! Give yourself a little cheer and keep an eye out for notifications about activity on your pull request. Some project managers are able to give guidance on how to fix code that isn't quiiiiiite right - listen to them! This is a great way to improve your skills in a real-world scenario.

Happy coding!

Support the Python Software Foundation!
https://support.google.com/youtube/?p=donate_FAQ