Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying path for lines of code (tokei) badge #5890

Closed
make-github-pseudonymous-again opened this issue Dec 1, 2020 · 3 comments
Closed
Labels
needs-upstream-help Not actionable without help from a service provider service-badge Accepted and actionable changes, features, and bugs

Comments

@make-github-pseudonymous-again
Copy link

make-github-pseudonymous-again commented Dec 1, 2020

📋 Add functionality similar to the custom path version of GitHub repo file count to the Lines of code (via tokei) badge (See the size category). The line count should be the one output by tokei :path.

I am simply reiterating desire expressed by @feluelle and @jnm2 in #2731.

Currently the only way to achieve a similar result is to add a .tokeignore file which may be annoying for various reasons.

@chris48s
Copy link
Member

chris48s commented Dec 1, 2020

Our badges are based on scraping the ones from by tokei.rs (we don't run tokei as a library in our own codebase)
https://github.com/XAMPPRocky/tokei#badges
I don't think their service has that feature, so I think this is a feature request for the upstream.

@chris48s chris48s added the service-badge Accepted and actionable changes, features, and bugs label Dec 1, 2020
@make-github-pseudonymous-again
Copy link
Author

Here is a link to the relevant upstream issue: XAMPPRocky/tokei_rs#2.

@paulmelnikow paulmelnikow added the needs-upstream-help Not actionable without help from a service provider label Jul 9, 2021
@paulmelnikow paulmelnikow changed the title Allow to specify path for lines of code (tokei) badge. Allow specifying path for lines of code (tokei) badge Jul 9, 2021
@paulmelnikow
Copy link
Member

Since this is out of Shields' hands I'm going to close this, though feel free to reply here if there is any new information, and if it becomes actionable by shields we can reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-upstream-help Not actionable without help from a service provider service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

3 participants