Skip to content

Contractor Onboarding

Welcome. This page covers everything you need on day one: accounts to request, how to pick up your first issue, and where to get help.

Accounts Checklist

Request the following before starting any work.

Account How to get access
GitHub Email hello@liflode.com — request access to the Curious-Owl11 org
Linear Email hello@liflode.com — request an invite link
docs.liflode.com Email hello@liflode.com — site is behind Cloudflare Access, you need to be added to the allowlist
Infisical Only if your role requires direct secrets access — most contractors do not need this. Ask if unsure.

Allow 1 business day for access to be provisioned.

Development Environment

  1. Clone your assigned repo — find it in the Curious-Owl11 GitHub org
  2. Follow the README — each repo has its own setup instructions
  3. Python runtime (Windows): C:\Python313\python.exe (Python 3.13)
  4. Secrets — never hardcode credentials. Follow the repo README for local secret setup.

First Issue

  1. You will receive a Linear invite and a direct link to your assigned issue
  2. Read the full issue description before starting — steps and acceptance criteria are explicit
  3. Check for dependency constraints — do not start an issue that is blocked by another
  4. Create a branch from main using the naming convention below

Branch naming

<type>/<ticket>-<slug>

Examples:

feat/IT-1234-add-webhook
fix/IT-1567-null-pointer-on-import
chore/IT-1890-update-deps

Commit format

Use Conventional Commits:

feat: add webhook handler for Linear events
fix: handle null response from Seek API
chore: update Python dependencies
docs: add contractor onboarding page
refactor: extract db helper into shared module
test: add unit tests for email classifier
ci: fix flaky GitHub Actions step

PR Process

  1. Open your PR as a draft as soon as you push your first commit
  2. Link the Linear issue in the PR description using the issue identifier (e.g. IT-1234)
  3. Ensure CI passes (all checks green) before requesting review
  4. Move the PR from draft to Ready for Review
  5. 1 approval required before merge
  6. Merge using squash merge

Questions and Help

Type of question Where to ask
Code review feedback Comment on your open PR
Access issues Email hello@liflode.com
Architecture and design See docs/architecture/ and docs/reference/
Process questions See the rest of this docs site