CCExtractor / CCExtractor/taskwarrior-flutter
chore: Ignore platform-generated build files to improve DX
- Langage dominant
- Dart
- Étoiles
- 244
- Forks
- 179
- Merge moyen
- 12 h 42 min
- PR mergées (30 j)
- 2
Description
### improvement idea
Currently,
when developers run `flutter pub get` or test the app locally, Flutter auto-generates platform-specific build files
> linux/flutter/generated_plugin_registrant.cc
> linux/flutter/generated_plugins.cmake
> macos/Flutter/GeneratedPluginRegistrant.swift
> pubspec.lock
> windows/flutter/generated_plugin_registrant.cc
> windows/flutter/generated_plugins.cmake
depending on local dependencies.
This creates dirty working directories and forces contributors to manually discard changes before committing.
To improve the Developer Experience (DX) and prevent unwanted files from being committed, these paths should be added to `.gitignore`.
### My proposed solution
> 1. I will append the specific paths of the auto-generated platform files to the `.gitignore` at the root of the project.
> 2. Run `git rm --cached ` to untrack these files from the Git repository history so they immediately stop causing merge conflicts for new branches.
By taking these simple steps, we completely automate ignore rules, keeping all future Pull Requests clean from randomly generated machine-specific code.
**I am currently working on a PR for this to help out the team.**
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le .gitignore à la racine et examinez les fichiers linux/flutter/generated_plugin_registrant.cc, linux/flutter/generated_plugins.cmake, macos/Flutter/GeneratedPluginRegistrant.swift, pubspec.lock et leurs équivalents Windows indiqués. Vérifiez leur statut de suivi actuel avec git avant de continuer. C'est terminé lorsque flutter pub get ou les tests locaux ne laissent plus ces chemins comme des modifications indésirables dans l'arbre de travail.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- flutter, git
- Domaine
- build-system, developer-experience
- Type d'issue
- Refactorisation
- Difficulté
- 1/5
- Temps estimé
- 1-3 heures
- Activité
- À l'abandon
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 25/100