GIT Architecture
Some Important Git Termonology
1.Branch
A branch is a parallel version of a repository. It is contained within the repository, but does not affect the primary or master
2.Clone
A clone is a copy of a repository that lives on your computer instead of on a website's server
3.Collaborator
A collaborator is a person with read and write access to a repository
4.Contributor
A contributor is someone who has contributed to a project by having a pull request merged but does not have collaborator access.
5.Diff
A diff is the difference in changes between two commits, or saved changes.
6.Fetch
Fetching refers to getting the latest changes from an online repository without merging them in. Once these changes are fetched you can compare them to your local branches (the code residing on your local machine).
7.fork
A fork is a copy of a repository on the server only. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.
8.Merge
Merging takes the changes from one branch (in the same repository or from a fork), and applies them into another.
9.Pull
Pull refers to when you are fetching in changes and merging them.
10.Pull request
Pull requests are proposed changes to a repository submitted by a user and accepted or rejected by a repository's collaborators.
11.Push
Pushing refers to sending your committed changes to a remote repository, such as a repository hosted on GitHub.
12.Repository
A repository is the most basic element of GitHub. They're easiest to imagine as a project's folder.
13.SSH key
SSH keys are a way to identify yourself to an online server, using an encrypted message. It's as if your computer has its own unique password to another service. GitHub uses SSH keys to securely transfer information to your computer.
14.Difference between Pull and Rebase
git pull and git rebase are not interchangeable, but they are closely connected.
git pull fetches the latest changes of the current branch from a remote and applies those changes to your local copy of the branch. Generally this is done by merging, i.e. the local changes are merged into the remote changes. So git pull is similar to git fetch & git merge.
Rebasing is an alternative to merging. Instead of creating a new commit that combines the two branches, it moves the commits of one of the branches on top of the other.
You can pull using rebase instead of merge (git pull --rebase). The local changes you made will be rebased on top of the remote changes, instead of being merged with the remote changes.
Hardware i use to record all my videos:
Laptop : https://amzn.to/34HuWwF
Mouse : https://amzn.to/34FwF5M
Keyboard : https://amzn.to/3ibV7Uc
EarPhone : https://amzn.to/2SQMV0Y
Boya Mic : https://amzn.to/3wQQa7A
#Selenium #SeleniumAutomation #SeleniumTesting #SeleniumTutorial #SeleniumTraining
#SeleniumEssentials #Automation #NareshShewakramani #SeleniumBasics #SeleniumByNareshShewakramani
#Seleniumbynaresh #SeleniumInterview #SeleniumQuestion #SeleniumTopQuestions #SeleniumInterview #interviewSelenium
Auf dieser Seite können Sie das Online-Video GIT Architecture mit der Dauer stunde minuten sekunde in guter Qualität ansehen, das der Benutzer Naresh Shewakramani 26 Oktober 2018 hochgeladen hat, den Link mit Freunden und Bekannten teilen, dieses Video wurde auf Youtube bereits 3,996 Mal angesehen und es wurde von 41 den Zuschauern gefallen. Viel Spaß beim Betrachtenden Zuschauern gefallen!
