DevTools writes devtools_options.yaml into a checkout the first time it runs. It records which DevTools extensions are enabled on this machine, nothing about the project, so it differs per checkout and is no use to anyone else. Ignored ahead of it appearing, because under jj, which tracks new files automatically, being ignored is the only way a file stays out of the next commit on its own. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
60 lines
1.2 KiB
Text
60 lines
1.2 KiB
Text
# Miscellaneous
|
|
*.class
|
|
*.log
|
|
*.pyc
|
|
*.swp
|
|
.DS_Store
|
|
.atom/
|
|
.buildlog/
|
|
.history
|
|
.svn/
|
|
migrate_working_dir/
|
|
|
|
# IntelliJ related
|
|
*.iml
|
|
*.ipr
|
|
*.iws
|
|
.idea/
|
|
|
|
# The .vscode folder contains launch configuration and tasks you configure in
|
|
# VS Code which you may wish to be included in version control, so this line
|
|
# is commented out by default.
|
|
#.vscode/
|
|
|
|
# Flutter/Dart/Pub related
|
|
**/doc/api/
|
|
**/ios/Flutter/.last_build_id
|
|
.dart_tool/
|
|
.flutter-plugins
|
|
.flutter-plugins-dependencies
|
|
.packages
|
|
.pub-cache/
|
|
.pub/
|
|
/build/
|
|
|
|
# Flutter DevTools writes this into a checkout the first time it runs. It
|
|
# holds local tool state (which DevTools extensions are enabled), not project
|
|
# configuration, so it differs per machine and belongs to nobody else.
|
|
devtools_options.yaml
|
|
|
|
# Symbolication related
|
|
app.*.symbols
|
|
|
|
# Obfuscation related
|
|
app.*.map.json
|
|
|
|
# Android Studio will place build artifacts here
|
|
/android/app/debug
|
|
/android/app/profile
|
|
/android/app/release
|
|
/android/build
|
|
|
|
# Rust wrapper crate (native/)
|
|
native/target/
|
|
|
|
# Rust cdylibs built into the APK by devbox run build-native-android
|
|
android/app/src/main/jniLibs/
|
|
|
|
# Patrol generates the bundle from the integration tests at run time
|
|
**/test_bundle.dart
|
|
.patrol.env
|