Tutorial · Part 7 · Choose an exercise

Take the workflow further

Keep your finished weather page, then try a branch comparison or one of the follow-up tutorials.

You have changed the page, checked AI edits, and recorded your work in Git. Keep this sample as a finished example. The follow-up tutorials start with fresh copies so you can see their changes clearly.

Compare the sample's other branch

The sample includes add-wind-chill, an unfinished experiment made before your edits. You can inspect it without changing the files you just finished.

  1. Click the weather Project Tab, then click Staging in the activity bar. Finish reviewing and committing any work you want to keep. Both file groups should be empty.
  2. Click Git in the menu bar, then click Branches. The Branches content tab opens.
  3. Find add-wind-chill and click its row to expand the details.
  4. In the Deltas section, click Compare. A diff opens for that branch and your current branch.
  5. Look at src/temperature.js in the comparison. The experiment adds work on a wind-chill calculation. Your more recent heading and forecast changes can also appear in the comparison because the branches have different histories.
  6. If the file list is not visible, click Files in the activity bar. Click index.html in the list. Your saved heading is still there. Comparing branches did not switch your checkout.

For the full set of branch actions, see Branches and Compare.

Try parallel tasks with QuickTree

A branch comparison shows two versions of a project. A worktree lets you open another branch in its own folder and Project Tab. That makes room for a second task while the first one is still in progress.

In Work in parallel with QuickTree, you will start two Assist tasks from a fresh sample, review each result, merge the changes, and remove the finished worktrees. The tutorial walks through the full process, including the destination branch and cleanup choices.

Take a change through GitHub

So far, your commits are only on this computer. In Issue to release with GitHub, you will publish a fresh sample to your own practice repository, write an issue, follow a failing test through GitHub Actions, and finish with a reviewed pull request and a release.

That tutorial includes a small check kit to download. It needs a GitHub account and Node.js; the QuickTree tutorial stays local.

Return to your own project

Click File in the menu bar, then click Open Project. Click Browse... and select a folder you already work in. Start by reading its files and commit history. When you ask an AI tool for a change, keep the same habit you practiced here: inspect the diff and check the result before committing.