Spenser Black

BTW I've used codecov.io on a few projects. I like its visualizations, and its GitHub integration can add checks to commits and PRs for coverage deltas.

Great! Would you want to add a coverage badge? The markdown can be found in the [settings page](https://app.codecov.io/gh/o2sh/onefetch/settings) (I don't have access to the settings).

To be honest I like both approaches. For unit tests, I think mocking is a great idea, but for integration tests I like creating temporary git repos. I like mocking...

Cleaning up old PRs and forks. Will probably delete the fork soon, but the refs in this PR should still be reachable via `refs/pull/NUMBER/head`.

> `--tracked` of course would be a more comfortable option but only for that specific usecase, while the proposed solution is extremely flexible, standard and generic. Yeah, after coming back...

>Have you tried with the go repository I linked and specifically mentioned as a reproducible non-working example? Ah, I see what you mean now. I skimmed over the man page...

Thinking on this a bit more, if `--file-list` is the chosen implementation, I think that this needs to be considered: `--file-list` would effectively point to an "allow list" -- it...

I'm going to be closing this because the initial request (`--tracked` flag) is definitely not in tokei's scope IMO. However, the ideas presented here in this conversation are pretty interesting,...

> I wouldn't add a maintainer who wasn't already a regular contributor who I felt understood the goals and intentions of the project. Just curious, do you currently feel like...

> the best answers to those questions for users would not be sustainably solved by adding more people. To be fair, when the main delay to a release is [a...