Auto-generated Pull Request for fix/list-plasmids-expression #611
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| # AGENTS.md | ||
|
|
||
|
|
||
| ## Essential Commands | ||
|
|
||
| ```bash | ||
| # Test | ||
| gotestsum --format pkgname-and-test-fails --format-hide-empty-pkg -- ./... | ||
|
|
||
| # Test (verbose) | ||
| gotestsum --format testdox --format-hide-empty-pkg -- ./... | ||
|
|
||
| # Watch mode | ||
| gotestsum --watch --format pkgname-and-test-fails --format-hide-empty-pkg -- ./... | ||
|
Comment on lines
+8
to
+14
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Description: Check if gotestsum is used in the project and verify command validity
# Check if gotestsum is in go.mod or referenced elsewhere
rg -n "gotestsum" --type=yaml --type=md --type=go
# Check for any test scripts or Makefile that might define the canonical test command
fd -t f -e mk -e sh -e bash -e zsh --exec rg -l "test"Repository: dictyBase/graphql-server Length of output: 323 🏁 Script executed: # Check if CLAUDE.md exists in the repository
fd -i claude
# Look for CI configuration files
fd -e yml -e yaml | grep -i ci
# Check go.mod for dependencies and tools
head -50 go.modRepository: dictyBase/graphql-server Length of output: 2130 🏁 Script executed: # Look for Makefile or similar test definitions
fd -e mk
# Search for any references to CI or workflow tests
rg -n "go test" --type=yaml --type=go --type=md -A 2Repository: dictyBase/graphql-server Length of output: 50 🌐 Web query:
💡 Result: gotestsum is a Go test runner that wraps go test -json and provides various output formats via the --format flag or GOTESTSUM_FORMAT environment variable. Official documentation is in the GitHub README at https://github.com/gotestyourself/gotestsum. Key formats relevant to the query: - pkgname (default): Prints a line for each package, using icons/color to indicate pass/fail/skip status. Icons customizable via --format-icons or GOTESTSUM_FORMAT_ICONS. For passing packages, shows minimal info; for failing packages, shows number of failures (e.g., "0 failed" implied by pass icon, explicit count for fails). - testdox: Prints a readable sentence for each test using gotestdox (e.g., ✔ TestUserAuth_Login (0.23s), ✖ TestPayment_Stripe (0.92s) --- FAIL: invalid API key). Shows pass/fail with icons and elapsed time. No exact format named "pkgname-and-test-fails" exists in the docs. The pkgname format handles test failures by showing failure counts and details in the post-run summary for failed packages. Use --hide-summary to control summary details (e.g., --hide-summary=skipped). Full list of common formats (run gotestsum --help for all): - dots: character per test - pkgname: line per package (default) - testname: line per test+package - testdox: sentence per test - standard-quiet: go test default - standard-verbose: go test -v Examples: gotestsum --format=pkgname ./... gotestsum --format=testdox ./... After formatted output, a summary shows failures, skips, errors, and DONE line (e.g., DONE 9 tests, 1 failure in 3.2s). Latest version info as of 2026-04-15: v1.13.1-0.20260415004743-3cf14356a16c. Citations:
Fix invalid gotestsum format flags in test commands. The test commands in lines 8 and 14 use an invalid format flag: Line 11 correctly uses Additionally, gotestsum is not listed in 🤖 Prompt for AI Agents |
||
|
|
||
| # Lint | ||
| golangci-lint run ./... | ||
|
|
||
| # Format | ||
| golangci-lint fmt | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document coding conventions and guidelines, not just commands.
The AI summary indicates that the removed
CLAUDE.mdfile contained Go coding conventions and repository guideline documentation (including style rules). This new file only documents essential commands, resulting in a loss of important developer guidance.Consider adding sections that cover coding standards, architectural patterns, and contribution guidelines to maintain the documentation that was previously available.
🤖 Prompt for AI Agents