Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @SMC17
33 changes: 33 additions & 0 deletions .github/ISSUE_TEMPLATE/1-bug.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
name: Bug report
description: Something does not build, crashes, or gives a wrong result.
labels: ["type: bug", "status: needs-triage"]
body:
- type: textarea
id: what
attributes:
label: What happened
description: What you ran, what you saw, and what you expected instead.
validations:
required: true
- type: textarea
id: repro
attributes:
label: Command that reproduces it
description: The smallest command or input that shows the problem, starting from a fresh clone if you can.
render: shell
validations:
required: true
- type: input
id: commit
attributes:
label: Commit or release
placeholder: "e.g. v1.4.1 or 3f2a9c1"
validations:
required: true
- type: input
id: env
attributes:
label: Toolchain and machine
placeholder: "e.g. Zig 0.16.0, macOS 26 on Apple M2"
validations:
required: true
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/2-feature.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
name: Feature or improvement
description: Propose something new or better.
labels: ["type: feature", "status: needs-triage"]
body:
- type: textarea
id: problem
attributes:
label: Problem
description: What you are trying to do and what gets in the way today.
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposal
description: What you would change. Alternatives you considered are welcome.
validations:
required: true
- type: textarea
id: done
attributes:
label: How we know it is done
description: The test, command or measurement that would show it works.
validations:
required: true
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/3-claim.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
name: Challenge a claim
description: A number, ratio or statement in this repo does not hold up when you check it.
labels: ["type: claim", "status: needs-triage"]
body:
- type: markdown
attributes:
value: |
Every public claim here should come with a command that reproduces it. If one does not hold on your machine, that is a bug in the claim, and this is the place to report it. Results that disagree are as welcome as ones that agree.
- type: input
id: where
attributes:
label: Which claim
description: Link to the file and line, or quote it.
validations:
required: true
- type: textarea
id: measured
attributes:
label: What you measured
description: Your numbers, and the command you ran to get them.
render: shell
validations:
required: true
- type: input
id: env
attributes:
label: Commit, toolchain, machine
placeholder: "e.g. 3f2a9c1, Zig 0.16.0 ReleaseFast, Ryzen 7950X Linux"
validations:
required: true
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: Report a security vulnerability
url: https://github.com/SMC17/yard/security/advisories/new
about: Please report security issues privately, not as an issue.
- name: How work is tracked across SMC17
url: https://github.com/SMC17/SMC17/blob/main/STANDARDS.md
about: Labels, proof levels, and what "done" means in every repo.
18 changes: 18 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
## What and why

<!-- One or two sentences. Link the issue: "Closes #123". -->

## Evidence

<!-- The command you ran and what it printed. For any performance or correctness claim:
commit, toolchain, machine, and the script. A claim without these is removed before merge. -->

```
```

## Checklist

- [ ] Tests pass from a fresh clone on the pinned toolchain
- [ ] Docs, STATUS.md and CHANGELOG (if present) updated for anything a user would notice
- [ ] No number in the docs that this PR's evidence does not back
- [ ] AI assistance, if any, is disclosed in this description
14 changes: 14 additions & 0 deletions .github/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
changelog:
exclude:
labels: ["status: wontfix"]
categories:
- title: Breaking changes
labels: ["breaking"]
- title: Fixes
labels: ["type: bug", "type: claim"]
- title: Features
labels: ["type: feature", "type: perf"]
- title: Documentation
labels: ["type: docs"]
- title: Other changes
labels: ["*"]
83 changes: 83 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at sean@sunlitmoon.online. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# yard

**[Status](STATUS.md) · [Roadmap](ROADMAP.md) · [Contributing](CONTRIBUTING.md) · [Issues](https://github.com/SMC17/yard/issues) · [Public roadmap](https://github.com/users/SMC17/projects/16)**

[![CI](https://github.com/SMC17/yard/actions/workflows/ci.yml/badge.svg)](https://github.com/SMC17/yard/actions/workflows/ci.yml)
[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
[![Zig: 0.16](https://img.shields.io/badge/Zig-0.16-orange.svg)](https://ziglang.org/)
Expand Down
5 changes: 5 additions & 0 deletions ROADMAP.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# yard roadmap

The issues are the source of truth; this file is a snapshot taken 2026-11-17.

No work is tracked yet. Ideas and bugs belong in [issues](https://github.com/SMC17/yard/issues); the roadmap is generated from them.
7 changes: 7 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Security policy

Report vulnerabilities privately through [GitHub security advisories](https://github.com/SMC17/yard/security/advisories/new), not in a public issue.

Include the commit, the toolchain, and the smallest input that triggers the problem. This project has one maintainer; expect an acknowledgement within 7 days and a plan within 30. Fixes are credited in the release notes unless you ask otherwise.

Only the latest release and `main` receive fixes.
10 changes: 10 additions & 0 deletions STATUS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# yard status

| | |
|---|---|
| Proof level | **unit-tested** (see [proof levels](https://github.com/SMC17/SMC17/blob/main/STANDARDS.md#proof-levels)) |
| Last verified | 2026-11-17, fresh clone, macOS on Apple M2 Max, Zig 0.16.0 |
| Command | `zig build test --summary all` |
| Result | 1688/1688 tests passed |

What comes next: [ROADMAP.md](ROADMAP.md) and the [open issues](https://github.com/SMC17/yard/issues).
Loading