exercism / exercism/dart

[Discussion] Should `pubspec.lock` be continued to be tracked?

Aperta
#201 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
discussion
Lingua principale
Dart
Stelle
60
Fork
97
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

I remember we removed `pubspec.lock` from exercises, But I see that the repo-level `pubspec.lock` is still being tracked. I generally prefer not tracking generated files because they introduce unnecessary noise in `git diff`s.

If there is use case I don't know about, please do tell. Otherwise we should stop tracking it.

Edit: Tracking `pubspec.lock` also distrupts the branching flow. A contributor might be working or reviewing multiple branches, due to the nature of how `pubspec.lock` is kept in sync with the `pubspec.yaml`, difference in `pubspec.lock`'s timestamp between branches requires running `pub get` again, which updates the `pubspec.lock` timestamp. So switching branches generally requires resetting the `pubspec.lock`

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.