Skip to content

docs: add local verification steps to CONTRIBUTING - #102

Open
kshivam4781 wants to merge 1 commit into
forthfate:mainfrom
kshivam4781:docs/local-verification-steps-v2
Open

kshivam4781 wants to merge 1 commit into
forthfate:mainfrom
kshivam4781:docs/local-verification-steps-v2

Conversation

@kshivam4781

Copy link
Copy Markdown

Closes #17. Supersedes #49 (that branch was 278 commits behind main and couldn't be cleanly updated, so this reopens the same change on a fresh branch off current main).

Adds a "Local verification" section to CONTRIBUTING.md, right after "Pre-commit", so a contributor can pick the right checks for the kind of change they made.

Addresses the review feedback on #49: the introductory sentence now distinguishes CI's frontend job (production build only) from the pre-commit hook (which runs ESLint), instead of implying CI runs both the same way.

Verified against the current main branch: the backend commands (uv run ruff check orbit/ backend/ tests/, PYTHONPATH=backend uv run pytest -q) and frontend commands (pnpm --filter agent-improvement-console-ui run lint / run build) match .github/workflows/ci.yml exactly as of this PR.

Added local verification instructions for different types of changes, including backend, frontend, and UI end-to-end changes.
@forthfate

Copy link
Copy Markdown
Owner

@kshivam4781 Thank you so much for putting this together! These local verification steps will be really helpful for contributors. One small thing: CI also runs pnpm run docs:build with strict validation for every PR. Would you mind adding that for documentation changes and updating the note that says no command is required?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document local verification steps for frontend, backend, and UI changes

2 participants