Team Workflows - Quiz

Create a new branch for a feature without switching away from your current branch, following your team's naming convention

Download new commits from the default remote without merging them, so you can inspect changes before integrating

Add a branch protection rule so that pull requests into the main branch require status checks to pass before merging

Stage changes only in the docs directory of a monorepo before opening a documentation review

Tag the current commit with a semantic version before cutting a production release

Which team workflow best fits a small team deploying multiple times per day from a single main branch?

In a hosted Git platform, which permission level should typically be given to someone who configures branch protection and integrations?

Why would a team define a CODEOWNERS file for a monorepo?

Which branching strategy explicitly separates long-lived master and develop branches plus dedicated release branches?

What is the main benefit of requiring status checks on a protected main branch?

Order the steps to onboard a new developer to a team Git workflow using feature branches and protected main

Drag and drop to reorder, or use the arrows.

Order the steps to configure branch protection and code review for main in a hosted Git repository

Drag and drop to reorder, or use the arrows.

Order the steps to prepare and tag a release in a Git Flow-style workflow

Drag and drop to reorder, or use the arrows.

Order the steps to update a feature branch in a monorepo with latest changes from main before opening a pull request

Drag and drop to reorder, or use the arrows.

You are on the branch release/2.0.0 preparing a production release. What will this command print?

1git branch --show-current

In a monorepo, you're currently inside the project-a directory but still on a shared branch feature/cleanup. What does this command output?

1git rev-parse --abbrev-ref HEAD

After tagging v1.4.3 on the current commit in your release management process, what will this command print?

1git describe --tags --exact-match

Your main branch is configured as the default upstream. What will this show while you are on main?

1git rev-parse --abbrev-ref --symbolic-full-name @{u}

Find the incorrect command in this workflow for creating a protected release branch and pushing it

Click on the line(s) that contain the bug.

git checkout main

git pull origin main

git branch release/1.2.0

git checkout release/1.2.0

git push origin main

Identify the incorrect command in this code owner review workflow

Click on the line(s) that contain the bug.

git checkout -b feature/joe/update-api

# edit files in src/api

git add src/api

git commit -m "Update API endpoints"

git push origin main

Spot the bug in this attempt to protect the production branch and merge a hotfix

Click on the line(s) that contain the bug.

git checkout production

git pull origin production

git checkout -b hotfix/login-timeout

# fix bug

git commit -am "Fix login timeout"

git push origin hotfix/login-timeout

Match each concept with its primary purpose in team Git workflows

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each access level with what it typically allows in hosted Git platforms

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match Git branching patterns with appropriate team scenarios

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Complete the commands to create a CODEOWNERS file for frontend and docs in a monorepo

Complete the commands to set up a local main branch to track the remote main for a new team member

Complete the commands to tag and push a semantic versioned release after merging a release branch

Click the line showing the currently checked-out branch when managing a monorepo

Click on the line to select.

  docs-update

* main

  feature/service-a-refactor

  release/2.0.0

Click the line indicating the code owner requested for a pull request touching backend files

Click on the line to select.

Reviewers

- @team-backend (required)

- @alice

Status checks

- ci/backend-tests (required)

Click the line that shows the semantic version tag used for a production release

Click on the line to select.

commit 9f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0 (tag: v3.2.1)

Author: Release Bot <bot@example.com>

Date:   Tue Nov 5 10:15:00 2024 +0000

    Release v3.2.1