chore: remove committed binaries and scratch dirs; tighten .gitignore #1

2026-04-18T11:52:05-07:00

nsatoshi commented

2026-04-18 11:52:05 -07:00

Summary

First PR in the 11-PR sequence to finish the explorer (see explorer-monorepo-completion-prompt.md). This one is pure repo hygiene — no behaviour change.

Changes

Remove three committed Go binaries (~54 MB total):
- backend/bin/api-server
- backend/cmd (a binary despite the path looking like a directory)
- backend/api/rest/cmd/api-server
Remove scratch / build output directories that were committed:
- out/ (Foundry build artifacts)
- cache/ (Solidity cache)
- test-results/ (Playwright)
Extend .gitignore so these paths — plus playwright-report/, .playwright/, and coverage/ — don't creep back in.

Why

Committed binaries bloat the repo, make diffs noisy, and hide what a build actually produces. Scratch dirs leak between contributors' machines and desync with the compiler/tooling versions they were produced on. Both classes belong in .gitignore and should be regenerated per build.

Verification

git diff --stat shows only .gitignore content + three Bin deletions + four small JSON deletions.
No Go source, config, or migration files changed. CI should behave identically (the build still compiles from backend/api/rest/cmd/main.go and backend/indexer/main.go).

Completion criterion advanced

1. Clean repo hygiene — "No binaries, build artifacts, or scratch dirs committed. .gitignore covers …"

Still outstanding in later PRs: secret purge from history, doc consolidation, .gitmodules decision.

## Summary First PR in the 11-PR sequence to finish the explorer (see `explorer-monorepo-completion-prompt.md`). This one is pure repo hygiene — no behaviour change. ## Changes - Remove three committed Go binaries (~54 MB total): - `backend/bin/api-server` - `backend/cmd` (a binary despite the path looking like a directory) - `backend/api/rest/cmd/api-server` - Remove scratch / build output directories that were committed: - `out/` (Foundry build artifacts) - `cache/` (Solidity cache) - `test-results/` (Playwright) - Extend `.gitignore` so these paths — plus `playwright-report/`, `.playwright/`, and `coverage/` — don't creep back in. ## Why Committed binaries bloat the repo, make diffs noisy, and hide what a build actually produces. Scratch dirs leak between contributors' machines and desync with the compiler/tooling versions they were produced on. Both classes belong in `.gitignore` and should be regenerated per build. ## Verification - `git diff --stat` shows only `.gitignore` content + three `Bin` deletions + four small JSON deletions. - No Go source, config, or migration files changed. CI should behave identically (the build still compiles from `backend/api/rest/cmd/main.go` and `backend/indexer/main.go`). ## Completion criterion advanced > **1. Clean repo hygiene** — "No binaries, build artifacts, or scratch dirs committed. `.gitignore` covers …" Still outstanding in later PRs: secret purge from history, doc consolidation, `.gitmodules` decision.

nsatoshi referenced this pull request

2026-04-18 12:31:05 -07:00

docs: rewrite README, add ARCHITECTURE.md (Mermaid), add API.md from swagger.yaml #11

nsatoshi merged commit e0311259ca into master

2026-04-18 12:34:58 -07:00

nsatoshi referenced this issue from a commit

2026-04-18 12:35:00 -07:00

Merge pull request 'chore: remove committed binaries and scratch dirs; tighten .gitignore' (#1) from devin/1776538258-chore-gitignore-and-artifacts into master

nsatoshi referenced this issue from a commit

2026-04-18 13:06:34 -07:00

Merge pull request 'chore: remove committed binaries and scratch dirs; tighten .gitignore' (#1) from devin/1776538258-chore-gitignore-and-artifacts into master

Sign in to join this conversation.