-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Using CLOC for github urls. #798
Comments
cloc would have to clone the repo (or download the project's .zip file) to count it. What would you want cloc to do with the download afterwards? Leave it be on your file system? Delete it? |
We can give a flag to choose the downloaded repo should stay in our file System or not . It gives more versatile options to the users . I think this would be a good choice compared to the deletion of repo and this way the user have some control over it . Thank you for your time and consideration. |
This could be very useful to me. btw love the tool, its very good! |
If I add a capability to work with git URLs, for example cloc https://github.com/inducer/pudb.git that would simply do the same thing as these two commands: git clone https://github.com/inducer/pudb.git cloc pudb/ I just don't understand the value in a new cloc capability to replace the two commands with one. What am I not getting? Are there other capabilities or benefits that I'm overlooking? |
The proposal suggests allowing cloc to analyze GitHub repositories directly from their URLs without the need for manual cloning. This enhancement aims to streamline the process and enhance user efficiency like reduced steps , user flexibility , Efficiency. |
Yes, manual cloning will be avoided-but of course cloc will need to do the clone under the hood. I'm not ruling this out, I just see little value added. |
yeah I understood the value of this , compared to other feat , it should be in the low priority level . And this is just the idea which might increase the flexibility of the tool , consider this enhancement in lower priority level ! |
I agree completely with @AlDanial on this one. Unix commands should do one thing well(TM) as much as possible. Adding capabilities already provide by other tools would bloat cloc and drive dev time away from it's core features. Just use the two commands folks, it's better that each command do it's own thing well!
|
Closing, as I won't implement this. |
Feat :
Let's take an example github URL : https://github.com/AlDanial/cloc.git
Cloc can able to count blank lines, comment lines, and physical lines of source code from the direct Github url.
For Example :
It would be nice if cloc works with direct Github repo's too !
The text was updated successfully, but these errors were encountered: