Skip to content

Latest commit

 

History

History
28 lines (21 loc) · 2.17 KB

workflow.md

File metadata and controls

28 lines (21 loc) · 2.17 KB

Assignment Workflow

  1. Fork the repository for the assignment, which should appear at github.com/YOU/REPOSITORY.
  2. Click the "Clone in Desktop" button on the right sidebar from your fork, not the original. (If you get a "permission denied" error later, you probably skipped this step.)
  3. Open the index.html file in a browser and open the Developer Tools.
  4. Modify the files, and add any files/libraries/assets you need.
  5. Make small commits as you go.
  6. Refresh the index.html page to see the results, and repeat.
  7. Explain your project in the README:
    • How it evolved (with photos is a plus)
    • Links/images/video of any inspiration or resources that were helpful
    • Feel free to put the above information in a blog post, and simply link from the README instead.
  8. Make sure all of your changes are committed.
  9. "Sync" your commits from the GitHub app.
  10. Create a pull request on the original repository.
  11. You can continue to push fixes and improvements while the pull request is Open – just add a comment in the pull request to let me know it's been updated.

Live Preview

Your solution will be live at http://USERNAME.github.io/REPOSITORY. Make sure this version works, since it's what will be looked at to give feedback. Note that after your initial push/sync, it may take up to ten minutes for the site to appear.

Automatic Style Checking

When the pull request is created, you should see a message saying that "the Travis CI build is in progress" – this means that your solution is being automatically checked for syntax errors. If this "build" ends up failing (which will show a red "X"), click through the "details" link and scroll to the bottom to see what the errors were. This automated feedback will help you write better code. If it's green checkmark, you're good to go.

Discussion

I will leave feedback in the pull request, so please respond with your thoughts and questions! You are welcome to open the pull request as a work-in-progress if you are stuck and want to ask a question – just mention @afeld to make sure I get the notification.