Version control

Works like Git, with a commit graph like GitHub Desktop or GitKraken. Your first week on a team repo: pull, branch, commit only the fix, merge a teammate's conflicting change, take a leaked key back out and push your branch.

Monday at Northfield Labs. Your clone of signin is a week old, and the terminal is open in it. (A made-up company. Start with git status.)

QuickCruit Git

2 changed files

src/lockout.py

Saved

"""Locking an account after too many wrong passwords."""

MAX_ATTEMPTS = 10
LOCK_MINUTES = 15


def should_lock(failed_attempts):
    """True once an account has failed too many sign-ins in a row."""
    return failed_attempts >= MAX_ATTEMPTS

No conflict markers

Practice laptop, built for you. Git and a small bash.

You're in ~/signin. Type git status to see where things stand, or help for the basics.

Ready

↑0 ↓0

signin · Week 1

Your first fix on signin

Jordan KowalskiEngineering Lead, Northfield Labs

Off the identity backlog, assigned to you:Accounts should lock after 5 wrong passwords in a row. The code allows 10.

Origin has moved since you cloned signin last week, so start from an up-to-date main. Fix it on a branch, one commit with just the fix and a message that says what it does, then push the branch. Main is protected, so it only lands through a pull request, and I'll review it there.

Your local debug.log and the log_level: debug line in config.yml stay out of the commit.

Northfield Labs and everyone here are made up. A practice repo, built for you.

Team chat

Messages from the team land here during the day.

1. Branch off an up-to-date main
2. Commit the fix, and only the fix
3. Merge main in and resolve the conflict
4. Take the key back out
5. Push your branch

Checks read the repo as it stands: branches, commits, files and origin. Check as often as you like.