Skip to content

Onboarding Guide

Welcome to Tenacious. This guide gets you productive quickly and points you to the standards you'll use every day. Read it first, then keep the standards bookmarked.

For new engineers

Day one

  1. Confirm you've been added to the right GitHub team (your manager handles this) - access comes from team membership, not from being added to repos individually.
  2. Read the Home page to understand why we have standards.
  3. Skim each standard once (links in the left sidebar) so you know what exists and where to find it later.

Your first change

Follow this flow - it's the same one for every change you'll ever make here:

  1. Create a branch from main following the Branching Standard (e.g. feature/ACME-123-add-export).
  2. Make your change. Keep secrets out of the code (see Secrets Management).
  3. Push and open a pull request using the template, following the Pull Request Standard.
  4. Make sure CI passes (see the CI/CD Standard).
  5. Get an approving review (see the Code Review Standard).
  6. Squash-merge, and delete your branch.

That's it. If you can do this loop comfortably, you know how we work.

For engineering managers

Starting a new project

The full process lives in the Repository Management Standard. The essentials:

  1. Apply the approved template structure with the integration command - it works for new and existing repos (see Integrating the template).
  2. Name it by convention: tenacious-<project> internally, or <client>-<project> for client work (with the client and project name in the repo description).
  3. Grant access to a team, never to individuals: a team named after the client for client work, or the internal team otherwise.

Then walk the full initialization checklist before development begins.

Adding and removing people

  • Add people to the relevant team; never add them as individual repository collaborators.
  • Remove people from the team when they leave the project - this revokes their access everywhere at once.

Editing these standards

This site is just Markdown. To propose a change:

  1. Branch from tenacious-standards.
  2. Edit or add a file in docs/.
  3. If you add a page, register it under nav: in mkdocs.yml.
  4. Open a PR following the Pull Request Standard.

Standards improve through the same review process as our code. If something here is wrong or outdated, fixing it is a welcome contribution.

Run the site locally

pip install -r requirements.txt
mkdocs serve
Then open http://127.0.0.1:8000 to preview your changes with live reload.