Get some practice in ๐
-
Fork this repository.
-
Copy the resulting git link.
-
git clone
this fork into yourmy-forked-repos
directory (review setup instructions). -
cd
into this repository. -
Immediately
git checkout -b your-name
(ex: git checkout -b rick-patci)
- Notice the "build passing" message icon in this README file? That's an import from Travis CI - just one of many continuous integration tools used by organizations and project teams all over the world! We use Travis CI in this class to help us lint code being submitted (in your case as the developer, it will test any PRs you submit for proper linting).
- Let's try and get a "build failing" message instead, so we can see what that's like:
- Within the
starter-code
directory, open up thewat.js
file and remove the semicolon from the end of the line and save the file. - Back in our terminal, type
git status
to ensure any changes were actually being tracked by git. - Let's take this a step further and type
git diff
- git diff displays changes line by line, with red lines being the previous code, and green lines being the new code. - We should see a red line with the semicolon at the end, and a green line with a missing semicolon at the end.
- Now to exit this diff, we type
q
to return back to the terminal. - Now, assuming we are still inside of the
starter-code
folder, we can: git add wat.js
git commit -m 'remove semicolon to make the lint test fail'
git push origin
your-name- Head over to GitHub to make a PR from the branch with your name.
- This will take you to a comment section that has some "bolierplate" (pre-strutured) comments. It is your task to fill in the blanks and follow the instructions ๐
- Once finished with the PR comments section, submit the PR, copy the resulting link that you see in your URL path at the top of the browser window after creating the Pull Request (to submit in Canvas).
- Now let the test finish, and see what the result is!
When finished, submit to Canvas the links to your PR as well as the sample Issue that you created.