Refine agent branch naming and Go formatting guidance

This commit is contained in:
maze committed 2026-10-29 18:40:07 +01:00
1 parent 07dc1ec5b3
commit d489a9b85c
4 files changed
+3 -10

No files matched your search

+1 -4
View File
@@ -1,6 +1,6 @@
# Coding conventions
- Use idiomatic Go, `gofmt`, and the surrounding package's naming and import style.
- Use idiomatic Go, `goimports`, and the surrounding package's naming and import style.
Extend existing contracts instead of introducing parallel registries or layers.
- Wrap propagated errors with useful context and `%w`. Use `errors.Is` or
`errors.As` when callers need to recognize them.
@@ -17,6 +17,3 @@
- Put focused tests beside implementations. Cover parsing, malformed input,
detection precedence, failures and recovery with temporary files or fake servers.
Unit tests should run without physical GPIO, displays or a live MPD instance.
Adapted from [Flow's coding guide](https://github.com/onflow/flow-go/blob/master/docs/agents/CodingConventions.md),
with BeatGlow-specific lifecycle, logging and hardware guidance.
-2
View File
@@ -17,5 +17,3 @@
documentation after checking the implementation; keep separate logic fixes scoped.
- Wrap prose around 100 characters where practical. Avoid documenting obvious
implementation steps or adding repetitive boilerplate.
Adapted from [Flow's Go documentation guide](https://github.com/onflow/flow-go/blob/master/docs/agents/GoDocs.md).
-2
View File
@@ -16,5 +16,3 @@
critical without evidence or claim a fix is verified on hardware without testing it.
- Finish with concise results, links to changed files or the PR, and material
limitations. Never report a PR created when only its branch was pushed.
Adapted from [Flow's operational guide](https://github.com/onflow/flow-go/blob/master/docs/agents/OperationalDoctrine.md).