mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
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>
27 lines
1.5 KiB
Markdown
27 lines
1.5 KiB
Markdown
# 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](artefact/git/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](tools/ghcr/authentication.md) for the full setup guide.
|
|
|
|
## Step-by-Step Flow 🪜
|
|
|
|
1. Create or update your fork.
|
|
2. Create a branch in your fork with the right prefix. See [branch.md](artefact/git/branch.md).
|
|
3. Make one focused change at a time.
|
|
4. Run the relevant local checks. See [testing.md](actions/testing.md).
|
|
5. Push the branch to your fork.
|
|
6. Wait until the CI in your fork is green. See [pull-request.md](artefact/git/pull-request.md) for required CI scope.
|
|
7. Open a [Pull Request](artefact/git/pull-request.md).
|
|
8. Address review feedback in your fork. See [review.md](actions/review.md).
|
|
|
|
## Discussion 💬
|
|
|
|
Questions and discussion about the contribution workflow MAY be raised in the [Infinito Nexus Hub](https://hub.infinito.nexus). A dedicated thread on forking and contributing is available [here](https://s.infinito.nexus/forking).
|