INFO 2480-61: Website Database Implementation
  • Syllabus
  • Welcome Letter
  • Week 1: Software and Setup
    • Folder Structure
    • Git: Getting Started
      • Installing a Git Client
      • Creating a Local Repository
      • Making Changes and Merging them
      • Git Wrap Up
    • Git: Github
      • Creating a New Account
      • Creating a Repo on Github
      • Cloning and Forking
      • Cloning a Repo from Github
      • Pushing Changes to Github.com
      • Github: Adding a Collaborator
    • Command Box
      • Downloading the Software
      • Unzipping and Running the Software for the first time
      • Using CommandBox And Installing the UML-Info package.
      • Setting Up Your Local Server
      • Last Step
    • IDE ( Integrated Development Environment )
      • VS Code
      • IntelliJ
    • Journal
  • Week 2: Review of HTML and CSS
    • Making Point In Time and Working Branches
    • Opening our Project from Week 1 and Starting our BoxLang server
    • HTTP Calls and Requests
    • Making a Static Website Dynamic
    • Creating The Management Index.bxm
    • Creating An HTML Form with Bootstrap
    • Last Steps
  • Week 3: Working Forms and our First Table
    • Data Types
    • Case Types and Naming Conventions
    • Database Tools and Your First DB
      • Installing MySql WorkBench
      • Connecting to your MySQL database
      • Creating Your First Table
    • Working Forms
      • Separation of Concerns
      • Configuring Our Site To Use Our Database
      • Capturing Your Form Data
      • Creating Our Server Side Logic
  • Week 5: SQL and Modelling
    • Our Project And Its Users
    • Introduction to SQL
    • Completing our Articles page.
      • Adapting manageArticles.bxm to display existing articles in the database
      • Completing ManageArticles.bxm to Edit Existing Articles.
      • Making Active Articles Appear On The Public Page
  • Week 6: Managing Books
    • Introduction To Modelling
    • Our Data Models
    • Adapting Our Management Page To Be Multi-Tool
    • Creating The Manage Books Page
    • Adding Search To Our Front Index Page
  • Week 7: Working with Selects, Files, WYSIWYG and more.
    • Adding WYSIWYG Capabilities
    • Adding WYSIWYG to the Manage Books Tool
    • Adding Images To Our Store
    • Creating Our Publisher Select Control
  • Week 9: Joins and Better Searching
    • Displaying Our Publisher
    • Searching By Publisher
    • Creating a Browse by Genre
      • Adapting Our Database
      • Building our Queries: Part 1
      • Assigning Genres to a Book in our AddEdit.bxm page
      • Building our Queries: Part 2
      • Building the GenreNav.bxm
      • Adapting The Details.bxm Page to Search By Genre
  • End of Project Checkllist
Powered by GitBook
On this page
  1. Week 1: Software and Setup
  2. Git: Github

Cloning and Forking

PreviousCreating a Repo on GithubNextCloning a Repo from Github

Last updated 4 months ago

Goal: By the end of this document, you will understand what Cloning and Forking mean when it comes to git.

Previously, we created a git repository on our local machine, made a branch, made some changes and then checked that branch and those changes back in again. All of that happened on our local machine. , makes it easy to find other projects which we would either like to contribute to by adding a feature or fixing bug.

To do that, we usually copy the entire repository down to our local machine so we can work on it. When we make that copy, we now have a LOCAL copy and a REMOTE copy. The remote copy is still in the original owners account. This is called CLONING. When we clone a repo, we create a local repo on our machine, perhaps make a branch to use to make edits and then check those changes back into our local repo. If we choose to, and we have permission, we can then PUSH those changes back up to the remote repository. If it is not our account or we don’t have permission, we can create something called a PULL REQUEST which allows the account owner to look over your changes and choose to accept them or not.

Conversely, when you copy a repo from one account on Github to another account on Github ( such as your own ) it is called FORKING. The intention here is that you will clone the repo you forked onto your local machine and the forked repo will act as your remote repo. All changes you make will be checked into the repo on your account, not the original owners. If down the road, you wish the original owner to consider accepting your changes into their project, you would then create a PULL REQUEST (PR) or MERGE REQUEST (MR) for that owner to look over your changes and choose to merge them into their project or not.

In this class you will use a repo you create in your own Github.com account and use that to share your work with me.

Key points

  • Copying a repository from an account online is called cloning.

  • Copying a repository from an online account to another online account is called forking.

  • When you want changes you’ve made in one repo to be merged into a repo owned or managed by someone else, you create a pull request or merge request.

Github.com