{"id":172,"date":"2018-12-04T22:17:34","date_gmt":"2018-12-04T22:17:34","guid":{"rendered":"https:\/\/pressbooks.library.ryerson.ca\/wafd\/?post_type=chapter&#038;p=172"},"modified":"2019-11-15T17:48:46","modified_gmt":"2019-11-15T17:48:46","slug":"submitting-coding-assignments-and-using-github","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/","title":{"raw":"Submitting Coding Assignments and Using GitHub","rendered":"Submitting Coding Assignments and Using GitHub"},"content":{"raw":"<strong>Note:\u00a0<\/strong>If you are here as part of a course, please read on. Otherwise, submitting coding assignments is not required.\r\n\r\n<hr \/>\r\n\r\nMost assignments that follow are various inaccessible web page widgets that we will ask you to make accessible by rewriting their code (HTML, CSS, or JavaScript). If you are participating here as part of a course, you will need the link to a live web page with your solution. Before the code is reviewed, the page will be checked for accessibility (using ChromeVox and other tools).\r\n\r\nIt is your decision where you want to host the pages that you will submit for review. If you have your own domain and server space, you can upload completed assignments there and submit the URL. Another option is to submit the URL of a file on GitHub to <a href=\"https:\/\/raw.githack.com\">GitHack<\/a> (<a href=\"https:\/\/raw.githack.com\">https:\/\/raw.githack.com<\/a>),\u00a0then submit the URL to the output it generates as your assignment submission.\r\n\r\nFeel free to <a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">download the activity files<\/a> from our repository now, or if you are going to use GitHub, keep reading for instructions on how to fork it to your own account.\r\n\r\nIf you don\u2019t have a website, we recommend using GitHub as your platform for submitting assignments. Below we describe GitHub and GitHub Pages. If you are familiar with using GitHub or you have your own web server, you can skip the rest of this page or just scan it.\r\n<h2>Set Up a GitHub Account<\/h2>\r\nIf you do not already have one, you should create a GitHub account. For any developer, it is an invaluable tool for sharing and collaborating on code development. A GitHub account is free. Though you can download the activity files from GitHub, then unzip them and work from a local directory on your hard drive, we recommend creating a fork of the activity files to your own account and cloning your fork into a local directory. Follow the link below to set up an account, then read on.\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #3c3;\"><strong>Toolkit:<\/strong> <a href=\"https:\/\/github.com\/join\">Join GitHub<\/a><\/div>\r\n<h2>Set Up a Local Git Environment<\/h2>\r\nDepending on the operating system you are using, there are specific versions of Git for each platform. You may choose to use a Git client, or you may choose to use Git from the command line. Here we will present command line options. If you choose to use a client, see the documentation associated with the client for details on cloning, committing, pulling, and pushing.\r\n\r\nFor Windows and Mac users, if you are going to use a client instead of working from a command line, we suggest installing SourceTree. GitHub Desktop is a good alternative if you prefer to use an open source client. Feel free to choose another Git client if you like.\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #3c3;\"><strong>Toolkit:<\/strong> Download <a href=\"https:\/\/www.sourcetreeapp.com\/\">SourceTree<\/a>\u00a0or <a href=\"https:\/\/desktop.github.com\/\">GitHub Desktop<\/a> if you need a desktop Git client application.<\/div>\r\nFor Linux users you can use your system\u2019s package manager to install Git for command line use. On Ubuntu, for instance, at the command prompt you can run <code>apt-get<\/code> as the root user to install Git:\r\n\r\n<i>#&gt; <strong>sudo apt-get install git<\/strong><\/i>\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> For more about <a href=\"https:\/\/www.digitalocean.com\/community\/tutorials\/how-to-install-git-on-ubuntu-14-04\">Git setup on Ubuntu<\/a> see the tutorial on DigitalOcean.<\/div>\r\nIf you are using another Linux distribution, use Google to find details on installing Git on your version of Linux.\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> For details on installing Git, <a href=\"https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-Installing-Git\">see the Git Book.<\/a><\/div>\r\n<h2>Assignment Submissions via GitHub<\/h2>\r\nMost of the assignments that follow require submitting a URL to a publicly accessible version of the widgets that are the focus of the activities.\r\n\r\nIf you need a place to post your activity assignments, GitHub Pages can be a good option. Or, you may just prefer to use GitHub Pages to organize your files so they are not cluttering your web server. You will create a fork of the activity files (<a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">learnaria.github.io<\/a>), rename the repository to create your own version, and either upload it to a site of your choosing or use GitHub Pages. The GitHub Pages option is outlined here.\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/pages.github.com\/\">Using GitHub Pages.<\/a><\/div>\r\nIf you choose to use GitHub Pages, follow these steps to create a copy of the files under your own GitHub account.\r\n<ol>\r\n \t<li style=\"list-style-type: none;\">\r\n<ol>\r\n \t<li>Logged into GitHub, find your way to<a href=\"https:\/\/GitHub.com\/learnaria\/learnaria.github.io\"> the activity files<\/a>, and fork that repository. The fork button is at the top right of the GitHub screen while viewing a repository. This creates a copy of the repository under your own GitHub account where you will work from.<\/li>\r\n \t<li>After you have forked the activity files, go into the settings for that repository and change the name from learnaria.github.io to [username].github.io, where username is your GitHub account username. This will automatically create your GitHub Pages website at <strong><em>https:\/\/[username].github.io<\/em><\/strong>.<\/li>\r\n \t<li>Now you will want to create a clone of your forked activity files repository on your computer, through which you will do your work. From the command line issue the following command to create a clone of the forked version of the activity files you created, where [username] is your GitHub account username. You can also copy the https link from a field that opens when you click on the \u201cClone or download\u201d button in your repo.\r\n<i style=\"text-align: initial; font-size: 1em;\">#&gt;<\/i><strong style=\"text-align: initial; font-size: 1em;\"><i> git clone <\/i><\/strong><\/li>\r\n \t<li>If you are using SourceTree, click on \u201c+ New Repository\u201d and choose \u201cClone from URL\u201d and enter the above URL into the \u201cSource URL\u201d field. Set the \u201cDestination Path\u201d to your preferred work directory.<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ol>\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/help.github.com\/articles\/cloning-a-repository\/\">Cloning a repository.<\/a><\/div>\r\nYou should now have a copy of the activity files available locally that you can edit and commit back as your assignment updates, which become part of your GitHub Pages website.\r\n\r\nNote that it can take a few seconds or a minute for changes committed to your GitHub Pages repository to actually show up on the website.\r\n<h2>If You Already Have a GitHub Pages Site<\/h2>\r\nTo add the files to an existing GitHub Pages site, open the settings for the forked repository you created. In the GitHub Pages section shown in the screenshot below, choose the Source (typically, the master branch) and click Save. This will create a subdirectory under your existing GitHub Pages site with the name of the forked repository (i.e.,\u00a0<a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">learnaria.github.io<\/a>).\r\n\r\nYou may want to rename the repository to something shorter (e.g., learnaria) before enabling it in GitHub Pages. This would produce a URL to the activity files, something like:\r\n\r\n<strong>https:\/\/[username].github.io\/learnaria\/<\/strong>\r\n\r\n[caption id=\"attachment_158\" align=\"alignnone\" width=\"781\"]<img src=\"http:\/\/pressbooks.library.ryerson.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2.png\" alt=\"screenshot of the GitHub Pages settings\" class=\"wp-image-158 size-full\" width=\"781\" height=\"380\" \/> <strong>Figure:\u00a0<\/strong>A screenshot of the GitHub Pages settings[\/caption]\r\n<h2>Basic Git Commands<\/h2>\r\nYou do not need to be an expert Git user, but you should know a few basic commands if you are working from a command prompt. The commands you\u2019ll likely use are the following:\r\n<div style=\"border: 1px solid black; padding: 1em;\">\r\n\r\n<strong>git status<\/strong> \u00a0(displays a list of changed and untracked files)\r\n\r\n<strong>git add<\/strong> [filename] (prepares a files for committing)\r\n\r\n<strong>git commit<\/strong> -m \u201c[message]\u201d (describe the nature of the commit)\r\n\r\n<strong>git push<\/strong> [origin master] (sends the committed change to your GitHub repository master branch)\r\n\r\n<strong>git diff<\/strong> [filename] (shows the changes in a file)\r\n\r\n<\/div>\r\nOf course there are many other potential commands, but these are the most common. If you are using a Git client, such as SourceTree, these commands will be clickable in the UI buttons and menus. For more about using Git from the command line, see the Git Book.\r\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/git-scm.com\/book\/en\/v2\">The Git Book.<\/a><\/div>\r\n<h2>What the Activity Files Look Like<\/h2>\r\nHere is what to expect once you have successfully set up the activity files. You\u2019ll note that the widgets are inaccessible. Your job throughout the activities will be to fix the accessibility of each widget.\r\n<div style=\"height: 500px; width: 100%; overflow: hidden;\">[h5p id=\"1\"]<\/div>\r\n<!--https:\/\/learnaria.github.io-->","rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_80 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-69e3eb570a3b6\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-69e3eb570a3b6\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#Set_Up_a_GitHub_Account\" >Set Up a GitHub Account<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#Set_Up_a_Local_Git_Environment\" >Set Up a Local Git Environment<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#Assignment_Submissions_via_GitHub\" >Assignment Submissions via GitHub<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#If_You_Already_Have_a_GitHub_Pages_Site\" >If You Already Have a GitHub Pages Site<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#Basic_Git_Commands\" >Basic Git Commands<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/chapter\/submitting-coding-assignments-and-using-github\/#What_the_Activity_Files_Look_Like\" >What the Activity Files Look Like<\/a><\/li><\/ul><\/nav><\/div>\n<p><strong>Note:\u00a0<\/strong>If you are here as part of a course, please read on. Otherwise, submitting coding assignments is not required.<\/p>\n<hr \/>\n<p>Most assignments that follow are various inaccessible web page widgets that we will ask you to make accessible by rewriting their code (HTML, CSS, or JavaScript). If you are participating here as part of a course, you will need the link to a live web page with your solution. Before the code is reviewed, the page will be checked for accessibility (using ChromeVox and other tools).<\/p>\n<p>It is your decision where you want to host the pages that you will submit for review. If you have your own domain and server space, you can upload completed assignments there and submit the URL. Another option is to submit the URL of a file on GitHub to <a href=\"https:\/\/raw.githack.com\">GitHack<\/a> (<a href=\"https:\/\/raw.githack.com\">https:\/\/raw.githack.com<\/a>),\u00a0then submit the URL to the output it generates as your assignment submission.<\/p>\n<p>Feel free to <a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">download the activity files<\/a> from our repository now, or if you are going to use GitHub, keep reading for instructions on how to fork it to your own account.<\/p>\n<p>If you don\u2019t have a website, we recommend using GitHub as your platform for submitting assignments. Below we describe GitHub and GitHub Pages. If you are familiar with using GitHub or you have your own web server, you can skip the rest of this page or just scan it.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Set_Up_a_GitHub_Account\"><\/span>Set Up a GitHub Account<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>If you do not already have one, you should create a GitHub account. For any developer, it is an invaluable tool for sharing and collaborating on code development. A GitHub account is free. Though you can download the activity files from GitHub, then unzip them and work from a local directory on your hard drive, we recommend creating a fork of the activity files to your own account and cloning your fork into a local directory. Follow the link below to set up an account, then read on.<\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #3c3;\"><strong>Toolkit:<\/strong> <a href=\"https:\/\/github.com\/join\">Join GitHub<\/a><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Set_Up_a_Local_Git_Environment\"><\/span>Set Up a Local Git Environment<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Depending on the operating system you are using, there are specific versions of Git for each platform. You may choose to use a Git client, or you may choose to use Git from the command line. Here we will present command line options. If you choose to use a client, see the documentation associated with the client for details on cloning, committing, pulling, and pushing.<\/p>\n<p>For Windows and Mac users, if you are going to use a client instead of working from a command line, we suggest installing SourceTree. GitHub Desktop is a good alternative if you prefer to use an open source client. Feel free to choose another Git client if you like.<\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #3c3;\"><strong>Toolkit:<\/strong> Download <a href=\"https:\/\/www.sourcetreeapp.com\/\">SourceTree<\/a>\u00a0or <a href=\"https:\/\/desktop.github.com\/\">GitHub Desktop<\/a> if you need a desktop Git client application.<\/div>\n<p>For Linux users you can use your system\u2019s package manager to install Git for command line use. On Ubuntu, for instance, at the command prompt you can run <code>apt-get<\/code> as the root user to install Git:<\/p>\n<p><i>#&gt; <strong>sudo apt-get install git<\/strong><\/i><\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> For more about <a href=\"https:\/\/www.digitalocean.com\/community\/tutorials\/how-to-install-git-on-ubuntu-14-04\">Git setup on Ubuntu<\/a> see the tutorial on DigitalOcean.<\/div>\n<p>If you are using another Linux distribution, use Google to find details on installing Git on your version of Linux.<\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> For details on installing Git, <a href=\"https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-Installing-Git\">see the Git Book.<\/a><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Assignment_Submissions_via_GitHub\"><\/span>Assignment Submissions via GitHub<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Most of the assignments that follow require submitting a URL to a publicly accessible version of the widgets that are the focus of the activities.<\/p>\n<p>If you need a place to post your activity assignments, GitHub Pages can be a good option. Or, you may just prefer to use GitHub Pages to organize your files so they are not cluttering your web server. You will create a fork of the activity files (<a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">learnaria.github.io<\/a>), rename the repository to create your own version, and either upload it to a site of your choosing or use GitHub Pages. The GitHub Pages option is outlined here.<\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/pages.github.com\/\">Using GitHub Pages.<\/a><\/div>\n<p>If you choose to use GitHub Pages, follow these steps to create a copy of the files under your own GitHub account.<\/p>\n<ol>\n<li style=\"list-style-type: none;\">\n<ol>\n<li>Logged into GitHub, find your way to<a href=\"https:\/\/GitHub.com\/learnaria\/learnaria.github.io\"> the activity files<\/a>, and fork that repository. The fork button is at the top right of the GitHub screen while viewing a repository. This creates a copy of the repository under your own GitHub account where you will work from.<\/li>\n<li>After you have forked the activity files, go into the settings for that repository and change the name from learnaria.github.io to [username].github.io, where username is your GitHub account username. This will automatically create your GitHub Pages website at <strong><em>https:\/\/[username].github.io<\/em><\/strong>.<\/li>\n<li>Now you will want to create a clone of your forked activity files repository on your computer, through which you will do your work. From the command line issue the following command to create a clone of the forked version of the activity files you created, where [username] is your GitHub account username. You can also copy the https link from a field that opens when you click on the \u201cClone or download\u201d button in your repo.<br \/>\n<i style=\"text-align: initial; font-size: 1em;\">#&gt;<\/i><strong style=\"text-align: initial; font-size: 1em;\"><i> git clone <\/i><\/strong><\/li>\n<li>If you are using SourceTree, click on \u201c+ New Repository\u201d and choose \u201cClone from URL\u201d and enter the above URL into the \u201cSource URL\u201d field. Set the \u201cDestination Path\u201d to your preferred work directory.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/help.github.com\/articles\/cloning-a-repository\/\">Cloning a repository.<\/a><\/div>\n<p>You should now have a copy of the activity files available locally that you can edit and commit back as your assignment updates, which become part of your GitHub Pages website.<\/p>\n<p>Note that it can take a few seconds or a minute for changes committed to your GitHub Pages repository to actually show up on the website.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"If_You_Already_Have_a_GitHub_Pages_Site\"><\/span>If You Already Have a GitHub Pages Site<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To add the files to an existing GitHub Pages site, open the settings for the forked repository you created. In the GitHub Pages section shown in the screenshot below, choose the Source (typically, the master branch) and click Save. This will create a subdirectory under your existing GitHub Pages site with the name of the forked repository (i.e.,\u00a0<a href=\"https:\/\/github.com\/learnaria\/learnaria.github.io\">learnaria.github.io<\/a>).<\/p>\n<p>You may want to rename the repository to something shorter (e.g., learnaria) before enabling it in GitHub Pages. This would produce a URL to the activity files, something like:<\/p>\n<p><strong>https:\/\/[username].github.io\/learnaria\/<\/strong><\/p>\n<figure id=\"attachment_158\" aria-describedby=\"caption-attachment-158\" style=\"width: 781px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/pressbooks.library.ryerson.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2.png\" alt=\"screenshot of the GitHub Pages settings\" class=\"wp-image-158 size-full\" width=\"781\" height=\"380\" srcset=\"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2.png 781w, https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2-300x146.png 300w, https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2-768x374.png 768w, https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2-65x32.png 65w, https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2-225x109.png 225w, https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-content\/uploads\/sites\/57\/2018\/12\/githubpages_2-350x170.png 350w\" sizes=\"auto, (max-width: 781px) 100vw, 781px\" \/><figcaption id=\"caption-attachment-158\" class=\"wp-caption-text\"><strong>Figure:\u00a0<\/strong>A screenshot of the GitHub Pages settings<\/figcaption><\/figure>\n<h2><span class=\"ez-toc-section\" id=\"Basic_Git_Commands\"><\/span>Basic Git Commands<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>You do not need to be an expert Git user, but you should know a few basic commands if you are working from a command prompt. The commands you\u2019ll likely use are the following:<\/p>\n<div style=\"border: 1px solid black; padding: 1em;\">\n<p><strong>git status<\/strong> \u00a0(displays a list of changed and untracked files)<\/p>\n<p><strong>git add<\/strong> [filename] (prepares a files for committing)<\/p>\n<p><strong>git commit<\/strong> -m \u201c[message]\u201d (describe the nature of the commit)<\/p>\n<p><strong>git push<\/strong> [origin master] (sends the committed change to your GitHub repository master branch)<\/p>\n<p><strong>git diff<\/strong> [filename] (shows the changes in a file)<\/p>\n<\/div>\n<p>Of course there are many other potential commands, but these are the most common. If you are using a Git client, such as SourceTree, these commands will be clickable in the UI buttons and menus. For more about using Git from the command line, see the Git Book.<\/p>\n<div style=\"margin: 1em 0; padding: 1em; border: 1px solid #ddd; border-left: 10px solid #0000ff;\"><strong>Suggested Reading:<\/strong> <a href=\"https:\/\/git-scm.com\/book\/en\/v2\">The Git Book.<\/a><\/div>\n<h2><span class=\"ez-toc-section\" id=\"What_the_Activity_Files_Look_Like\"><\/span>What the Activity Files Look Like<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Here is what to expect once you have successfully set up the activity files. You\u2019ll note that the widgets are inaccessible. Your job throughout the activities will be to fix the accessibility of each widget.<\/p>\n<div style=\"height: 500px; width: 100%; overflow: hidden;\">\n<div id=\"h5p-1\">\n<div class=\"h5p-content\" data-content-id=\"1\"><\/div>\n<\/div>\n<\/div>\n<p><!--https:\/\/learnaria.github.io --><\/p>\n","protected":false},"author":100,"menu_order":2,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-172","chapter","type-chapter","status-publish","hentry"],"part":3,"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapters\/172","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/users\/100"}],"version-history":[{"count":42,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapters\/172\/revisions"}],"predecessor-version":[{"id":1950,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapters\/172\/revisions\/1950"}],"part":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/parts\/3"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapters\/172\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/media?parent=172"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/chapter-type?post=172"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/contributor?post=172"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/license?post=172"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}