Dominik Braun

@maniowy Thanks for your suggestions! They both make sense and I created two issues for them: #140 and #141.

> will tags be/optionally be output with the report as well? There's issue #202 for that. If no PR will be opened, I'll implement that myself within the next few...

GoReleaser automatically creates the changelog for the GitHub release based on the commit messages, doesn't it? That way, we wouldn't need release.py anymore.

Great! I'll enable GH Actions for this repository so we can get started.

So I enabled Actions and created the [default workflow](https://github.com/dominikbraun/timetrace/blob/main/.github/workflows/main.yml).

Note: Some tests for `Formatter` already are in `core/timetrace_test.go` and should be moved.

Absolutely: I planned to migrate to [afero](https://github.com/spf13/afero) for accessing the filesystem but didn't have the time yet. First, add a field of the type `afero.Fs` to the `fs.Fs` type and...

Hi @KonstantinGasser, yes, a stronger separation between the filesystem access and the business logic probably would make sense. On this occasion, we could also separate the `Filesystem` interface in more...

Yes, a rolling review would be nice here - and this probably will also affect some open PRs, hopefully the merge conflicts won't be too severe.

> Am I correct in my understanding that this issue just requires some work specifically on `askForCorfirmation()`? Absolutely. I think this is the only place where the user is asked...