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

Pushing Changes to Github.com

Goal: By the end of this document, you'll have added a file to your repo and pushed the change to Github.com

PreviousCloning a Repo from GithubNextGithub: Adding a Collaborator

Last updated 4 months ago

  1. Create a file called FirstFile.txt and put some text in it ( "Hello World" for example )

  2. Save the file into your local repo ( Sites\UML\webDatabaseImplementation\ongoingWork ? )

  3. Open your project in SourceTree and click on File Status. You should see your new file in the Unstaged Files section.

  4. Stage your file by clicking on Stage All or click on in and choose Stage Selected.

  5. Enter a commit message and commit it.

  6. Click on the PUSH icon at the top of the page

IF YOU RUN IN TO SECURITY ISSUES CONTINUE ON

  1. Go to Github.com and login.

  2. Click on your Avatar in the upper right and choose SETTINGS

  3. Click on Developer Settings in the left hand menu

  4. Expand the Personal access tokens menu on the left and choose Tokens (classic)

  5. At the top, click on Generate new token (choose classic again). You might be asked to authenticate again.

  6. Give your Token a name (can be anything - general access is perfectly fine)

  7. Select the checkbox next to repo to select all items in the repo section.

  8. Click on Generate Token

  9. IMPORTANT: COPY THIS TOKEN TO A FILE AND KEEP IT SAFE. YOU CAN NOT ACCESS IT AGAIN AFTER YOU CLOSE THIS WINDOW AND WILL HAVE TO GENERATE A NEW TOKEN.

  10. Back in your project in Source Tree, click on Settings in the upper right

  11. Under the Remotes Tab, click on the row for orgin then click Edit

  12. In the URL / Path box, IN FRONT OF THE EXISTING URL, paste your token followed by an @ sign. The contents of this box will then be token@github.com/whatever/your/site/path/is.git

  13. Click OK then OK to close all the windows.

  14. Try to Push to Github again.

  15. If you are still having issues, see your instructor.