| Previous Lecture | Lecture 17 | Next Lecture |
Lecture 17, Tue 02/16
Tue Discussion: Starting on the Legacy Code Projects
W21 Legacy Code Projects
| Section | Repo | Prod | QA | PRs | Issues | Kanban |
|---|---|---|---|---|---|---|
| 5pm | proj-ucsb-courses-search | prod | qa | PRs | Issues | Kanban |
| 6pm/7pm teams 1,3 |
proj-ucsb-cs-las | prod | qa | PRs | Issues | Kanban |
| 6pm/7pm teams 2,4 |
proj-mapache-search | prod | qa | PRs | Issues | Kanban |
W21 Kanban boards
Each of your teams has a Kanban board, shown in this table:
| 5pm | 6pm | 7pm | |
|---|---|---|---|
| 1 | team-5pm-1 | team-6pm-1 | team-7pm-1 |
| 2 | team-5pm-2 | team-6pm-2 | team-7pm-2 |
| 3 | team-5pm-3 | team-6pm-3 | |
| 4 | team-5pm-4 | team-6pm-4 |
Kanban Board Columns
Your Team’s Kanban board is where we’ll track your work on the legacy code repos for the rest of the quarter.
It has five columns as shown here:
| Planning | Todo | In Progress | In Review | Done |
|---|---|---|---|---|
| Your teams epic, and issues in the planning stages | Issues that are fully ready for someone on the team to pick up and work on | Issues that someone on the team is currently actively working on | Issues for which there is a pull request ready for review or being reviewed | Issues where the PR has been merged to main |
Issues
The staff has created some “issues” for you to work on, currently in the “Planning” column.
Issues start in the planning column, and stay there until the team has looked over them and decided they are ready to be picked up by a team member.
Then they go to to the “Todo” column.
Issues in “todo” can be picked up by any team member, or pair, or “mob” (three or more team members.)
When they are picked up, you assign yourself to the issue and move it to the “In Progress” column.
Creating a branch
When you start working on a story, you create a branch of the repo, and you start working on the issue in that branch.
e.g. if you are on team team-5pm-3 and your story is to fix the footer, you might decide to call your branch 5pm-3-fixFooter.
git clone ssh-url-of-repo-goes-here
cd repo-name
git checkout main
git checkout -b 5pm-3-fixFooter
PLEASE ALWAYS prefix your branch name with the name of your team (e.g. 5pm-3, 7pm-1).
Then make a comment on the issue with the branch name.
Then start working on the issue.
Write meaningful commit messages!
Your team will be graded on a random sample of its commit messages. So please hold one another accountable for writing good ones.
Here’s some advice: https://ucsb-cs156.github.io/topics/git_commit_messages/
git push origin branch-name
You are no longer pushing to main. You are pushing to your branch name, and then you’ll do a Pull Request.
We’ll talk more about pull requests in lecture tomorrow.