Skip to content

chore: exclude local AI workspaces from source and build artifacts - #19

Merged
ronag merged 1 commit into
nxtedition:masterfrom
ronag:codex/ignore-ai-workspaces-20261010
Oct 10, 2026
Merged

ronag merged 1 commit into
nxtedition:masterfrom
ronag:codex/ignore-ai-workspaces-20261010

Conversation

@ronag

@ronag ronag commented Oct 10, 2026

Copy link
Copy Markdown
Member

Exclude local Claude, Codex, Cursor, Aider, and hidden private workspace state from source and build artifacts. Use recursive Docker patterns at repository and existing build-context roots.

Validation on c807884f100a1df0cc497269763635126a170ec0:

  • 84 Git ignore sentinel checks, including nested paths.
  • 1 Docker ignore configuration checked; the common recursive patterns passed a real Linux Docker build-context test with root and nested sentinels.
  • Git diff checks pass.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Unanchored exceptions unintentionally expose nested .npmignore and .dockerignore files.

0 open findings

What changed in this PR

Adds ignore rules to keep local AI workspace state out of source control and Docker build contexts.

Changes:

  • Adds Git exclusions for supported AI tools and private scratch files.
  • Adds recursive Docker build-context exclusions.
File Description
.gitignore Adds workspace exclusions and ignore exceptions.
.dockerignore Excludes workspace state recursively.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ronag
ronag marked this pull request as ready for review October 10, 2026 17:00
@ronag
ronag merged commit 1c8b51e into nxtedition:master Oct 10, 2026
6 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants