Skip to content

docs: state the shared Go rules in the same words - #470

Merged
retr0h merged 1 commit into
mainfrom
docs/dedrift-shared-rules
Sep 3, 2026
Merged

docs: state the shared Go rules in the same words#470
retr0h merged 1 commit into
mainfrom
docs/dedrift-shared-rules

Conversation

@retr0h

@retr0h retr0h commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Compliance with global/documentation:

Where a convention binds several repositories, each states it in the same words, so a difference in wording means a difference in rule.

What was wrong

The formatting rule had four wordings across five repositories, and two of them changed its force:

gohai:         Go code is formatted by ...
nats-*:        Go code is formatted by ...
osapi:         Go code should be formatted by ...
orchestrator:  Go code should be formatted by ...

CI fails the build on it, so "should be" is not accurate. All five now state it the same way.

The generated-files exclusion was in four repositories and missing from gohai, which has two such files. Stated everywhere now.

nats-client and nats-server referenced [gofumpt] and [golangci-lint] without ever defining them, so both rendered as literal bracketed text instead of links. Definitions added.

The markdown formatting sentence had two wordings; it now reads the same in the four repositories that carry it.

What was deliberately left alone

Differences that exist because the repositories differ, not because the wording drifted:

  • each repository's own test commands and package paths (Testing)
  • branch-name examples chosen to match the repository (Branching)
  • orchestrator's rule about exercising a real HTTP server via httptest.Server
  • osapi's Prettier, ESLint and Docusaurus rules, which no other repository has

Measured before and after: 8 of 20 shared sections were identical, now 9. The two closest remaining (Test doubles at 98%, Testing at 93%) differ only for the reasons above.

Verification

just md-fmt-check passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_013oR5Gt9WPTTdPKdnShdL7L

global/documentation asks that a convention binding several repositories
be stated in each of them in the same words, because a difference in
wording is a difference in rule. The formatting rule had four wordings
across five repositories, and two of them said "should be formatted"
where the others said "is formatted". CI enforces it, so it is not
advice.

The exclusion for generated files was stated in four repositories and
missing from gohai, which has two such files.

nats-client and nats-server referenced [gofumpt] and [golangci-lint]
without ever defining them, so both rendered as literal text rather than
links.

Sections that differ because the repositories differ are left alone:
each one's test commands, package paths and branch-name examples, and
osapi's Prettier and Docusaurus rules.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013oR5Gt9WPTTdPKdnShdL7L
@retr0h
retr0h force-pushed the docs/dedrift-shared-rules branch from cbc2bb5 to 30b5f61 Compare September 3, 2026 01:19
@codecov

codecov Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #470   +/-   ##
=======================================
  Coverage   99.94%   99.94%           
=======================================
  Files         484      484           
  Lines       22877    22877           
=======================================
  Hits        22865    22865           
  Misses         12       12           

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 6a7e284...30b5f61. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@retr0h
retr0h merged commit 6d4bb11 into main Sep 3, 2026
12 checks passed
@retr0h
retr0h deleted the docs/dedrift-shared-rules branch September 3, 2026 01:35
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