mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
kevinveenbirkenbachandClaude Sonnet 4.6
2457d0e13c
- Add Recording Tests section: Playwright codegen (built-in) and playwright-recorder (Docker/X11-based) with usage examples - Replace duplicated spec/env requirement blocks with links to their SPOT pages in docs/agents/files/role/ - Extend Development Procedure to include optional recording step Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Contribution Flow
This repository uses a strict fork-first workflow.
- You MUST NOT commit directly to
main. - You MUST do all work in your own fork.
- You MUST open Pull Requests from your fork back to the main repository.
Why this matters:
mainMUST stay stable.- Shared CI resources are limited.
- Broken experimental work MUST NOT run in the main repository.
Step-by-Step Flow
- Create or update your fork.
- Create a branch in your fork with the right prefix — see branch.md.
- Make one focused change at a time.
- Run the relevant local checks — see testing.md.
- Push the branch to your fork.
- Wait until the CI in your fork is green — see pull-request.md for required CI scope.
- Open a Pull Request.
- Address review feedback in your fork — see review.md.
Discussion
Questions and discussion about the contribution workflow MAY be raised in the Infinito Nexus Hub.
A dedicated thread on forking and contributing is available here.