pre-pr-checks

Install the pinned version with pip install ruff==0.15.12, then run ruff check . and ruff format --check . from the repo root. The pin matters because formatting rules shift between ruff releases and an unpinned local ruff can disagree with CI.

Run git fetch flagos main first, verify the ref date with git log, then git rebase flagos/main. Check git log --oneline <old-base>..flagos/main for your own commit subjects, since a commit already merged upstream will conflict with itself and should be dropped.

The lint workflow runs first and every other job declares needs: lint, so a formatting slip skips the build and integration jobs entirely. Run the two ruff commands locally before pushing to avoid a red lint that tells you nothing about the actual change.

On vendor boxes the torch environment lives in the system interpreter while bare python resolves to a conda install without torch, so pip installs ruff into the wrong environment. Use /usr/bin/python3 -m pip install ruff==0.15.12 and /usr/bin/python3 -m ruff check . instead.

Run ruff format --check . locally to name the files and ruff format --diff <file> to see the exact change, then apply ruff format. Amend the fix into the existing commit with git commit --amend --no-edit and push with git push --force-with-lease.

Do not hand-merge conflict markers in generated artifacts like csrc/aten/generated or backends configs. Take the upstream side with git checkout flagos/main -- <paths>, port only the generator change, re-run codegen, and confirm a second run produces no diff.