Video Link:- Session Video
ppt download :- ppt
GitHub :- Link
GitHub Desktop :- Link
GitHub Developers Pack :- Link
A repository is the most basic element of GitHub. They're easiest to imagine as a project's folder. A repository contains all of the project files (including documentation), and stores each file's revision history. Repositories can have multiple collaborators and can be either public or private.
Someone who manages a repository. This person may also be responsible for keeping the README and contributing files updated
A text file containing information about the files in a repository that is typically the first file a visitor to your repository will see.
A document that you can include with your project to let people know what they can and can't do with your source code.
Private repositories are only visible to the repository owner and collaborators that the owner specified.
A public repository can be viewed by anyone, including people who aren't GitHub users.
A repository that a user has decided to display prominently on their profile.
A fork is a personal copy of another user's repository that lives on your account. Forks allow you to freely make changes to a project without affecting the original repository. You can also open a pull request in the original repository.
A commit, or "revision", is an individual change to a file (or set of files). Commits usually contain a commit message which is a brief description of what changes were made.
Short, descriptive text that accompanies a commit and communicates the change the commit is introducing.
Pull requests are proposed changes to a repository submitted by a user and accepted or rejected by a repository's collaborators.
Merging takes the changes from one branch (in the same repository or from a fork), and applies them into another. This often happens as a "pull request" (which can be thought of as a request to merge).
Pull refers to when you are fetching in changes and merging them. For instance, if someone has edited the remote file you're both working on, you'll want to pull in those changes to your local copy so that it's up to date. See also fetch.
A clone is a copy of a repository that lives on your computer instead of on a website's server somewhere, or the act of making that copy. When you make a clone, you can edit the files in your preferred editor without having to be online. The repository you cloned is still connected so that you can push your local changes to the remote to keep them synced when you're online.
Also referred to as Pages. A static site hosting service designed to host your personal, organization, or project pages directly from a GitHub repository.
Issues are suggested improvements, tasks or questions related to the repository. Issues can be created by anyone (for public repositories), and are moderated by repository collaborators. You can also categorize an issue with labels and assign it to someone.
Markdown is an incredibly simple semantic file format, not too dissimilar from .doc, .rtf and .txt. Markdown makes it easy for even those without a web-publishing background to write prose (including with links, lists, bullets, etc.) and have it displayed like a website. GitHub supports Markdown and uses a particular form of Markdown called GitHub Flavored Markdown.
A difference that occurs between merged branches. Merge conflicts happen when people make different changes to the same line of the same file, or when one person edits a file and another person deletes the same file. The merge conflict must be resolved before you can merge the branches.
-> You can use GitHub Desktop to create and manage a Git repository without using the command line.
-> Part 1: Installing GitHub Desktop and authenticating your account
-> Part 2: Creating a new repository
-> Part 3: Publishing your repository to GitHub
a. GitHub Desktop is an application that enables you to interact with GitHub using a GUI instead of the command line or a web browser.
b. GitHub Desktop encourages you and your team to collaborate using best practices with Git and GitHub.
c. You can push to, pull from, and clone remote repositories with GitHub Desktop, and use collaborative tools such as attributing commits and creating pull requests.
d. GitHub Desktop is an open source project.
a. You can install GitHub Desktop on any supported operating system.
b. After you install the app, you will need to sign in and authenticate your account on GitHub. Authenticating allows you to connect to remote repositories on GitHub.
c. For more information on installing and authenticating, see "Setting up GitHub Desktop."
d. To install GitHub Desktop, visit the download page for GitHub Desktop.
e. In the File drop-down menu, click Options. In the options window, click Accounts and follow the steps to sign in. For more information on authenticating, see "Authenticating to GitHub."
a. If you do not have any repositories associated with GitHub Desktop, you will see a "Let's get started!" view, where you can choose to create and clone a tutorial repository, clone an existing repository from the Internet, create a new repository, or add an existing repository from your hard drive.
b. Click Create a tutorial repository and clone it.
c. Follow the prompts in the tutorial to install a text editor, create a branch, edit a file, make a commit, publish to GitHub, and open a pull request.
d. Creating a new repository
e. If you do not wish to create and clone a tutorial repository, you can create a new repository.
f. Click Create a New Repository on your Hard Drive....
g. Fill in the fields and select your preferred options.
h. "Name" defines the name of your repository both locally and on GitHub.
i. "Description" is an optional field that you can use to provide more information about the purpose of your repository.
j. "Local path" sets the location of your repository on your computer. By default, GitHub Desktop creates a GitHub folder inside your Documents folder to store your repositories, but you can choose any location on your computer.
k. Click Create repository.
a. When you create a new repository, it only exists on your computer and you are the only one who can access the repository. You can publish your repository to GitHub to keep it synchronized across multiple computers and allow other people to access it. To publish your repository, push your local changes to GitHub.
b. Click Publish repository in the menu bar.
c. GitHub Desktop automatically fills the "Name" and "Description" fields with the information you entered when you created the repository.
d. Click the Publish Repository button.
e. You can access the repository on GitHub.com
Learn to ship software like a pro.
There's no substitute for hands-on experience. But for most students, real world tools can be cost-prohibitive. That's why GitHub created the GitHub Student Developer Pack with some of their partners and friends: to give students free access to the best developer tools in one place so they can learn by doing.
Lots of free tools and courses… You have to just register in it with your college id and you will given the acess in 1-3 weeks.