Refine agent branch naming and Go formatting guidance
This commit is contained in:
4 files changed
+3
-10
No files matched your search
@@ -11,7 +11,7 @@ Raspberry Pi systems. Read the relevant code and these guides before changing it
|
||||
|
||||
- Create and switch to a feature branch before editing files or making commits.
|
||||
- Never commit directly on `main` or `master`.
|
||||
- Use descriptive branch names, such as `feat/mpd-fifo-output-monitoring`,
|
||||
- Use descriptive branch names, such as `feature/mpd-fifo-output-monitoring`,
|
||||
`fix/readme-images`, or `chore/agent-instructions`.
|
||||
- Continue on an existing feature branch when working on the same task. Create a
|
||||
separate branch from the target branch for unrelated work.
|
||||
@@ -74,7 +74,7 @@ GOOS=linux GOARCH=arm64 go test -exec /usr/bin/true ./player/...
|
||||
git diff --check
|
||||
```
|
||||
|
||||
Run `gofmt` on changed Go files. The Makefile has no test, lint, integration-test,
|
||||
Run `goimports` on changed Go files. The Makefile has no test, lint, integration-test,
|
||||
or generation targets. Linux wireless helpers prevent some packages from building
|
||||
natively on macOS. Report cross-compilation separately from executed tests and
|
||||
hardware verification. Use race tests on Linux when changing shared state.
|
||||
|
||||
Reference in new issue
Block a user