exercism / exercism/dart

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

Open
#201 2 comments 0 reactions 0 assignees View on GitHub
discussion
Dominant language
Dart
Stars
60
Forks
97
PR merge metrics
No merged PRs in 30d

Description

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`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.