Skip to content

docs: point Go conventions at the capability - #73

Merged
retr0h merged 2 commits into
mainfrom
docs/go-code-standards
Aug 16, 2026
Merged

docs: point Go conventions at the capability#73
retr0h merged 2 commits into
mainfrom
docs/go-code-standards

Conversation

@retr0h

@retr0h retr0h commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Implements specify-go-code-standards section 2, now that osapi-io/specs#77 has merged.

CONTRIBUTING.md stops restating the shared Go conventions and points at the capability. What stays is the commands a contributor runs, and whatever is genuinely specific to this repository.

Nothing was dropped without a home — every rule removed is stated in go-code-standards.

🤖 Generated with Claude Code

The shared conventions are specified once in go-code-standards.
CONTRIBUTING.md keeps the commands a contributor runs and whatever is
genuinely specific to this repository.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Thank you for contributing to this project! 😊🕹️

@codecov

codecov Bot commented Aug 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Impacted file tree graph

@@            Coverage Diff            @@
##              main       #73   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           14        14           
  Lines         3217      3217           
=========================================
  Hits          3217      3217           

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 758ff79...8c82224. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

The first pass replaced the shared Go conventions with a pointer,
which left a contributor unable to learn how to write code here
without reading another repository. It also dropped the suite naming
convention entirely, since the capability did not yet state it.

Keep the substance and the examples; the pointer establishes which
statement is authoritative.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@retr0h
retr0h merged commit 29e2be3 into main Aug 16, 2026
9 checks passed
@retr0h
retr0h deleted the docs/go-code-standards branch August 16, 2026 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant