Skip to content

chore: Enhance .gitignore with React Native patterns#17

Merged
sl0thentr0py merged 1 commit intomainfrom
chore/enhance-gitignore-react-native
Jan 28, 2026
Merged

chore: Enhance .gitignore with React Native patterns#17
sl0thentr0py merged 1 commit intomainfrom
chore/enhance-gitignore-react-native

Conversation

@antonis
Copy link
Contributor

@antonis antonis commented Jan 28, 2026

Summary

Enhances the repository's .gitignore to properly handle React Native reproductions by adding comprehensive ignore patterns for:

React Native Specific

  • Generated native folders (ios/, android/)
  • Metro bundler cache and health checks
  • Build artifacts (Pods, Gradle, Xcode builds)
  • Platform-specific files (Podfile.lock, local.properties, .gradle)
  • Lock files (package-lock.json, yarn.lock)

Development Tools

  • Claude Code local settings (.claude/settings.local.json)

Why

Following the creation of the React Native reproduction in #16, we noticed that generated folders like ios/ and android/ were showing as untracked files. These are auto-generated by the React Native CLI and should never be committed to the repository.

Changes

  • Added comprehensive React Native patterns
  • Added Claude Code local settings pattern
  • Organized patterns with clear comments for maintainability

This ensures future React Native reproductions won't accidentally include generated code.

Add comprehensive ignore patterns for React Native reproductions:
- Generated native project folders (ios/, android/)
- Metro bundler cache and health checks
- Build artifacts (Pods, .gradle, build folders)
- Platform-specific files (Podfile.lock, local.properties)
- Lock files (package-lock.json, yarn.lock)
- Claude Code local settings

This prevents accidental commits of generated code in future React Native
reproductions and keeps the repository clean.
@antonis antonis requested a review from sl0thentr0py January 28, 2026 14:12
@sl0thentr0py sl0thentr0py merged commit e1b5308 into main Jan 28, 2026
6 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