search

wert007 / commit-analyzer

Gets the time somebody worked on something from `git log`
MIT License
1 stars 1 forks source link

[Feature Request] Initial Milestone and / or Project #13

Open kevinmatthes opened 2 years ago

kevinmatthes commented 2 years ago

In #5, you wrote you consider a release the persisting of a completed project. I would like to ask you, @wert007, to create an initial milestone and / or project in order to have something like a To-Do-List with changes prerequisite for such a first completed project level.

Remember, the Cargo.toml specifies an initial version and I would consider it possible to reach this initial stable project state with meaningful functionalities and features.

wert007 commented 2 years ago

As I already wrote very early on, this is more of a little side project to me. So I also have no grant vision for it. Maybe one could look at other repository analyzer and see what features they have. But I don't know.. 😅

kevinmatthes commented 2 years ago

I did not expect any immense funding for this project, too. ("grant" = fund, financial support; "grand" = great)

But in contrast, I am about to integrate the tool into an important automation pipeline. This is why I tried to implement and / or request the changes I require for the integration. The goal is to extract the time spent in a given Git repository and to add it to an Excel sheet with fixed expectations regarding formats and positions.

If possible, I could also move the automation pipeline's functionalities into commit-analyzer directly. And, I think that @Ranplax might be interested in this tool, as well.

wert007 commented 2 years ago

But why do you need/want a release for that? That does not sound like an important step to integrate it into an automation pipeline. 😅

kevinmatthes commented 2 years ago

There is a version configured in your Cargo.toml. If you will never publish a release since software has the property of never being finished, why there is version configured? It is a bit confusing. And hard to cite. I expected corresponding releases to be published when a certain amount of features is implemented.

kevinmatthes commented 2 years ago

It is no problem when there never will be a release, after all. Feel free to close this issue. It just originates from the confusion about the version field in your configuration file.

wert007 commented 2 years ago

That version is auto generated, when you create a new project with cargo. Like I already said, you have my blessing to just not cite this project at all and just use it anyway. They would be a requirement in my opinion for a release, but I don't have a list of features, that are missing from this project.

So yeah, a release is rather improbable, at least in the time range, that you and @Ranplax would need it. 😅

NiklasLeukroth commented 2 years ago

I did not expect any immense funding for this project, too. ("grant" = fund, financial support; "grand" = great)

But in contrast, I am about to integrate the tool into an important automation pipeline. This is why I tried to implement and / or request the changes I require for the integration. The goal is to extract the time spent in a given Git repository and to add it to an Excel sheet with fixed expectations regarding formats and positions.

If possible, I could also move the automation pipeline's functionalities into commit-analyzer directly. And, I think that @Ranplax might be interested in this tool, as well.

While i do obviously think the work of @wert007 is great and should be appreciated by everyone, i wonder why you had me in mind specifically for this project @kevinmatthes ? :D

kevinmatthes commented 2 years ago

I thought that you also often need to write the time you spent working on Git projects to Excel files, @Ranplax.

kevinmatthes commented 2 years ago

How about a binary crate release? One could then install commit-analyzer using Cargo.