See also, this assignment on Canvas: https://ucsb.instructure.com/courses/14657/assignments/165182

Introducing Today’s Participation Activity

Today’s participation activity is an individual activity.

You may have already completed it, depending on how far along you are with your work on team01.

The task is to creating a branch other than main for working on your first issue, i.e. the “service” you were assigned to.

Note that the service you were assigned to is one of these:

  • JokeQueryService, LocationQueryService, PublicHolidayQueryService, TidesQueryService, UniversityQueryService, ZipCodeQueryService

You can see the branches that have been created for your repo here:

       
f23-5pm-1 branches f23-5pm-2 branches f23-5pm-3 branches f23-5pm-4 branches
f23-6pm-1 branches f23-6pm-2 branches f23-6pm-3 branches f23-6pm-4 branches
f23-7pm-1 branches f23-7pm-2 branches f23-7pm-3 branches f23-7pm-4 branches
  • Your branch name should be something like your name or initials, followed by the service you are working on, e.g. CG-Tides-Service or ChrisZipSvc etc.
  • If you see a branch with your initials, and your name, you have completed this first step.
  • If you don’t see your branch on Github, please look at Step 2.2a and complete this step today in lab

Once you are done with this step, please:

  • Verify that if you follow the link in the table avove to your branch, you find your branch listed.
  • Then, click on your branch name; you should end up at a URL such as this one (but with your team name and branch name):
    • https://github.com/ucsb-cs156-f23/team01-f23-5pm-1/tree/Jonathan-Location
  • Finally submit that link as your submission for p09 on Canvas

Then, you are encouraged to continue with team01.

You may want to skip ahead and do step 2.7 next (creating a Dokku deployment).

It can be done out of order (it doesn’t rely on steps 2.3, 2.4, 2.5, or 2.6), and it’s going to be one of the two participation activities for tomorrow. Why not get it out of the way today?

You can find that activity here: https://ucsb-cs156.github.io/f23/hwk/p11

Overall, your goal should be to have at least the service completed before class on Thursday, so that everyone in class can do at least one “code review”.

If you can have both the service and controller done before class on Thursday, that’s even better. It’s good to aim for a pace a bit faster than the deadlines so that there’s time to get help in case something goes wrong.