pragyaagnihh/github-workshop

GitHub Workshop

GitHub-Workshop

Terminologies

• Repository

  • 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.

• Issues

  • 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. Each issue contains its own discussion forum, can be labeled and assigned to a user.

• Markdown

  • Markdown is a 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.

• Clone

  • 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. With your clone you can edit the files in your preferred editor and use Git to keep track of your changes without having to be online. It is, however, connected to the remote version so that changes can be synced between the two. You can push your local changes to the remote to keep them synced when you're online.

• Fork

  • 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. Forks remain attached to the original, allowing you to submit a pull request to the original's author to update with your changes. You can also keep your fork up to date by pulling in updates from the original.

• Collaborator

  • A collaborator is a person with read and write access to a repository who has been invited to contribute by the repository owner.

• Contributor

  • A contributor is someone who has contributed to a project by having a pull request merged but does not have collaborator access.

• Pull request

  • Pull requests are proposed changes to a repository submitted by a user and accepted or rejected by a repository's collaborators. Like issues, pull requests each have their own discussion forum. For more information, see "About pull requests."

  Learning objectives

• Understand Git - A version control system (VCS) for tracking changes in computer files and coordinating work on those files among multiple people.

  • What is Git? Git
  • Installation
  • Git Basics Git Basics

• Understand GitHub and how it can be used to collaborate on projects with a team.

  • What is GitHub? The world’s largest community of developers to discover, share, and build better softwares
  • What is a repository?
  • How to use issues?
  • How to Markdown? Mastering Markdown - GitHub Guides
  • How to handle notfications? (settings -> notifications)
  • What is the GitHub Flow? Understanding the GitHub Flow
  • How to propose and collaborate on changes?
  • What are some other resources?

• Use GitHub pages to turn your GitHub repositories into elegant websites to showcase your portfolio, projects, documentation and anything else that you want to share with the world. GitHub Pages

Resources

• GitHub Glossary
• GitHub Pages