Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/func/func.logging.php on line 510
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/logging.php on line 54
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/logging.php on line 60
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/init.php on line 481
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/sessions.php on line 74
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/sessions.php on line 76
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/sessions.php on line 85
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/sessions.php on line 86
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/sessions.php on line 93
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/func/func.core.php on line 1836
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/cron.php on line 105
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/func/func.logging.php on line 49
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/func/func.logging.php on line 79
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/include/func/func.logging.php on line 86
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/include/func/func.logging.php:510) in /var/www/html/include/get_language.php on line 165
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /var/www/html/product.php on line 82
INVALID SQL: 1064 : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_BIG_SELECTS=1' at line 1
SQL QUERY FAILURE:SET OPTION SQL_BIG_SELECTS=1
INVALID SQL: 1064 : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_BIG_SELECTS=1' at line 1
SQL QUERY FAILURE:SET OPTION SQL_BIG_SELECTS=1
eClasses.org�::�Course Catalog�::�Introduction to Git and GitHub
eClasses.org :: Course Catalog :: Introduction to Git and GitHub

Introduction to Git and GitHub (P105)

Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.

If you are a web designer or developer and want to keep every version of an image, file or resource, it is very wise to use a Version Control System (VCS). A VCS allows you to: revert files back to a previous state, revert the entire project back to a previous state, review changes made over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.

Using a VCS also means that if you screw things up or lose files, you can generally recover easily. In addition, you get all this for very little overhead.

Although there are dozens of version control systems on the market, some of the world's most renowned projects (like the Linux Kernel, Ruby on Rails, or jQuery) are using Git as their VCS of choice.

In this class, we will review the steps of installing Git (Mac or Windows), understand basic file command-line syntax, review the workflow of version control in general, setup of the Git software, create repository to store our sample web project, work through real-world scenarios in using Git and GitHub in a team environment.

Note: We will be using the commands-line interface (Mac or Windows) solely to properly learn and understand underlying concepts.

Objectives for this class:

  • Review of version control and its usages.
  • Why would you want to use a version control system (VCS)?
  • Overview of Git and its workflow.
  • Command-line vs GUI tools.
  • Installation of software on Windows and Mac.
  • Basic file command-line syntax
  • Setting up a online GitHub
  • Creating an updating a repository
  • Git administration tasks: logging, committing, branching, and merging files
  • Project management with Git and GutHub

Applicable Job Roles: web designer, web developer, webmaster, web application developers

Outline
Week 1: Introducing version control systems (VCS)
  • How version control works
  • Components of Git
  • Installing Git tools for Windows or Mac
  • Setting up a local repository
  • Starting out with our initial project files
  • Reviewing file and folder command-line syntax
  • Adding and committing our first update to our local repository
Wee 2: Getting into Git
  • Three stages of our project (working directory, staging, and repository)
  • Three stages of a file (unmodified, modified, and staged)
  • Understanding workflow
  • Basic and most common Git commands:
    • init
    • add
    • commit
    • status
    • log
  • Updating our project: use case scenarios
Week 3: GitHub
  • Overview of projects
  • Setting up an account
  • Adding your SSH Keys
  • Updating our project: push an existing repository online
  • Pulling updates from remote repository
Week 4: Git and GitHub Workflow
  • Updating our project: Managing team members
  • Creating a new branch
  • Merging and cloning projects
  • Resolving conflicts between updates
  • Working as a collaborator on GitHub
    • Updating and managing issues
    • Closing issues
    • Creating your own projects
    • Working with team members
Prerequisites
  • No prerequisites for this class.
Requirements
  • You will need either a Windows or Mac machine to download the Git software.

Books:
 No book is required for this class.

Additional information:

Your place in the course is confirmed by your payment. Introductory courses are intended for students with no experience in the subject matter and are seeking beginner level training.

Refund Policy: Please read our Terms and Refund Policy before registering for this course.

Additional Cost: Book and software might be required for the course. Read the Requirements and Book section for more information. Course fee does not include the book and software cost .

How eClasses Work:Instructors post lectures (text-based, no video or audio), reading selections, and hands-on assignments once a week in the online classroom. Students can discuss the assignments with the instructor and amongst themselves in the classroom area. This format has no set meeting time, which allows students to attend class at a time most convenient to them, yet still provides logically organized communication between class participants. Students can apply for the completion certificate after finishing the class.

Student CenterStudent Center
Cart is empty
Introduction to Git and GitHub
Price: $200.00
Item No.: P105
Instructor: Frank Stepanski
Open Courses: No other sessions are scheduled for this course. You can add to your wish list and you will be notified when other sessions are scheduled.

Instructor's ProfileInstructor
Frank Stepanski has over 10 years experience in the IT field as a Web Developer. Frank has worked with technologies such as PHP, MySQL, ASP.NET, SQL Server as well as HTML, CSS and JavaScript. He has a Masters Degree in Software Engineering from Penn State University. He has also taught web programming classes at a local community college.
Before you register for this class, please read the Outline, Prerequisites, Requirements, Books, and Refund Policy sections carefully.
 

Testimonials

Rating
No testimonial available!