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
  1. Larger Projects

Sync the branches in GitHub

PreviousMerging the changes from my local machine to GitHubNextFinally

I now have three branches which have different status. If I go back to Code and select branches, I can see that Test and dev are 1 commit ahead of main. Hover your mouse above the numbers to clarify this.

We sync the branches using pull requests. We do this manually and we must accept the changes. If I click on New pull request, I see a summary of the changes.

Off screen (it is too big to show!) I see a description of all five files.

I click to Create pull request.

I now have the opportunity to approve this request. If this was a multi-programmer project, this sort of workflow would be critical.

I click to merge pull request and then to confirm.

I can see this was successful.

And when I go back to check the main branch, my files are there.