mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 13:17:07 +00:00
kevinveenbirkenbachandClaude Sonnet 4.6
ef7affff70
Adds a Repository Security Policies section to SECURITY.md pointing to the new branch protection and repository settings docs, fixes Matrix and phone contacts to proper hyperlinks, and cross-links the security policy files from pull-request.md, branch.md, and workflow.md. Applies documentation.md rules to all touched files (RFC 2119 usage, emoji placement, link text). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
33 lines
1.2 KiB
Markdown
33 lines
1.2 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.
|
|
- You MUST open Pull Requests from your fork back to the main repository.
|
|
|
|
These rules are enforced via branch protection — see [branch.md](security/branch.md) for the full policy.
|
|
|
|
Why this matters:
|
|
|
|
- `main` MUST stay stable.
|
|
- Shared CI resources are limited.
|
|
- Broken experimental work MUST NOT run in the main repository.
|
|
|
|
## Step-by-Step Flow
|
|
|
|
1. Create or update your fork.
|
|
2. Create a branch in your fork with the right prefix — see [branch.md](branch.md).
|
|
3. Make one focused change at a time.
|
|
4. Run the relevant local checks — see [testing.md](testing.md).
|
|
5. Push the branch to your fork.
|
|
6. Wait until the CI in your fork is green — see [pull-request.md](pull-request.md) for required CI scope.
|
|
7. Open a [Pull Request](pull-request.md).
|
|
8. Address review feedback in your fork — see [review.md](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).
|