IAC - Version Control
GITHUB
GITHUB
  • Background
  • Setting up GitHub
  • Windows
    • Working with a cloned repo
    • Populating a repo from local files
    • Integrate VSCode
  • Linux
    • Using SSH
    • GH Command Line
  • The Basics
    • Forks
    • Logs
    • Undoing Local Changes
  • Larger Projects
    • Setting up a repo
    • Creating my Branch Architecture Locally
    • Creating a Feature Branch
    • Creating my Branch Architecture on GitHub
    • Merging the changes from GitHub on my local machine
    • Merging the changes from my local machine to GitHub
    • Sync the branches in GitHub
  • Finally
Powered by GitBook
On this page

Finally

PreviousSync the branches in GitHub

Last updated 4 months ago

Using GitHub simply becomes second nature after a little while. Start by being methodical. Write a CHEAT SHEET for commands to do things and verify that it all works. When you need to revert to a previous version, you should be able to use your CHEAT SHEET. If I do not use these tools for a few months, I need my CHEAT SHEET! When I'm doing a development project, after a day, I'm fine again.

Before writing the cheat sheet, is a pretty good summary.

We have all developed practices in version control, and if you find any good, authoritative guides, please send them on to me!

When I'm coding, I'm doing one job at a time. Suppose in an assignment, I am adding code to check for previously discovered network addresses. At the start of my work, I'll make sure I have a clean repo. I make a change to main.py and I create a function in a separate file. I check that this works, and they do a commit with a meaningful message stating what I've done. I've changed two files, and neither change would make sense by itself. The commit is atomic in nature and encapsulates the entire change.

If I spend more than 30 minutes without a commit, I'm probably breaking my work up into chunks that are too big.

As always, my notes are out of date by the time I've written them. An added problem, how much can I cover in two weeks where students have never worked with GIT/GITHUB etc. before. Next steps, do the GitHub foundations course, it's free and it will look good on your CV. And it will also be more current than my notes.

this