Updating a Github Repository
- Thread starter godreborn
- Start date
- Views 803
- Replies 15
this might offer an explanation to the difference between pull vs fetch
https://www.geeksforgeeks.org/git-d...the command,changes into the local repository.
so I'm correct? I have to use git pull origin master for the master directory, but can I just use git pull by itself and it will know which branch was used?
hmm sorry I'm not sure, haven't not really messed with git to that extent. But what I gather you replace "master" with the branch "name" .. but can't confirm personally
Maybe check on stackoverflow: https://stackoverflow.com/questions...ository-with-changes-from-a-github-repository
let's say that the 3ds version of sm64 is updated on github, and I already have an earlier version of the source code on my computer, instead of deleting it and starting over, I could do something like git pull origin 3ds or main or whatever the branch is called, and it will update the necessary source code?
- Joined
- Jul 1, 2007
- Messages
- 331
- Trophies
- 1
- Age
- 34
- Location
- The far side of the moon
- Website
- Visit site
- XP
- 1,617
- Country
- Joined
- Jul 1, 2007
- Messages
- 331
- Trophies
- 1
- Age
- 34
- Location
- The far side of the moon
- Website
- Visit site
- XP
- 1,617
- Country
You use git checkout to switch branches, which requires you to specify the branch.
git pull updates the branch you have checked out.
Say I'm on the main branch and I want to switch to the 3ds branch:
git checkout 3ds
git pull
That's it, I'm now on the 3ds branch and it's up to date.
- Joined
- Jul 1, 2007
- Messages
- 331
- Trophies
- 1
- Age
- 34
- Location
- The far side of the moon
- Website
- Visit site
- XP
- 1,617
- Country
Fetch checks if there are any updates, pull actually pulls those updates. To pull a specific commit you use git checkout *commit hash*.
It's not recommended though because then you end up in a detached state, and generally speaking you want the latest code. I guess it doesn't matter quite so much if you're not making changes and pushing them to the source repo but it is messy and will put your local copy in a weird state.
It's not recommended though because then you end up in a detached state, and generally speaking you want the latest code. I guess it doesn't matter quite so much if you're not making changes and pushing them to the source repo but it is messy and will put your local copy in a weird state.
The "normal" way is to fetch all changes using "git fetch --all" and then update only the branches that you want to update to prevent conflicts with other branches of yours. Conflicts usually happen when you change a file that someone has made changes.
But the novice commands are:
git clone -> Download Repo to your Computer
git log -> to search older commits and their unique number
git checkout [BRANCH_NAME] -> Change Repo to the specified branch or change to a commit using the unique number
git pull -> Update Repo to your Computer to the latest changes
git add -> add changes
git commit -> persist locally changes with a message
git push -> send the persisted changes locally to online to allow others to see these changes
But the novice commands are:
git clone -> Download Repo to your Computer
git log -> to search older commits and their unique number
git checkout [BRANCH_NAME] -> Change Repo to the specified branch or change to a commit using the unique number
git pull -> Update Repo to your Computer to the latest changes
git add -> add changes
git commit -> persist locally changes with a message
git push -> send the persisted changes locally to online to allow others to see these changes
Adding to novice commands, git status -> lists "staged" changes
Useful to check before git commit
Rework of novice commands are:
git clone -> Download Repo to your Computer
git log -> to search older commits and their unique number
git checkout [BRANCH_NAME] -> Change Repo to the specified branch or change to a commit using the unique number
git pull -> Update Repo to your Computer to the latest changes
git add -> add or "stages" changes
git status -> lists "staged" changes
git commit -> persist locally changes with a message
git push -> send the persisted changes locally to online to allow others to see these changes
Similar threads
-
- Portal
-
-
-
@
Psionic Roshambo:
I have 16GBs of DDR4 that I have been using forever lol 3200 with extremely low latency -
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
32GBs is the baseline for 4K video editing these days and lots of recommendations for 64GBs but for games 16,GBs is honestly plenty for a long time.
-
-
-
-
-
-
-
-
like a 250 dollar kit back when DDR4 was Intel only