Environment TestandClaude Sonnet 4.6
83262816a3
- Move emojis after headline text (CONTRIBUTING.md, actions/, design/, tools/, tests/) - Replace em dashes with colons, semicolons, or complete sentences throughout - Add missing emojis to all headlines in exceptions.md, principles.md, services.md, shell.md, setup.md, pull-request.md, commit.md, act.md, docker.md, pr/README.md - Update H1 titles to reflect renamed directories (actions/, design/) - Fix broken relative links in workflow.md after directory moves - Fix full-path link texts in services.md (style.css.md, javascript.js.md) - Fix broken principles.md link to lint.md after testing/ → actions/testing/ move Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.5 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 and MUST open Pull Requests from your fork back to the main repository.
These rules are enforced via branch protection. See branch.md for the full policy.
Why this matters: main MUST stay stable, shared CI resources are limited, and broken experimental work MUST NOT run in the main repository.
Repository Configuration 🧩
Before running workflows you MUST configure the required secrets and credentials for the repository. This includes GHCR authentication for pushing and publishing container images. See authentication.md for the full setup guide.
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.