-
Notifications
You must be signed in to change notification settings - Fork 0
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
[metrics] gitlab raw data #8
Comments
List of metrics which were proposed in the earlier meeting by @valeriocos
|
Hi @valeriocos I was thinking of what all metrics can be defined from gitlab data.
Can we make this metric into two with much more clear meaning like
We can use them in the QMs too. WDYT? |
+1, thanks |
Sounds good! |
Sounds good @vchrombie |
+1 here as well :-) @vchrombie |
I have implemented the issue related metrics.
I think we can do the same thing for merge requests too
|
I left this at that time, but I'll complete it by the next PR. |
do you think we need to consider the comments as two different entities like I was thinking it would be better if we can keep them separate as we can specifically use |
Yes, good idea! let's keep them separated for the moment. |
I have completed working on this. I will add them to the PR. Also, I was going through the existing quality models, I saw one different metric in the Developer QM. It is the "number of issues attended". I think this has a different meaning than the number of comments. The Do you have any comments on this? |
It should be the number of issues that have at least one comment, which is not written by the issue reporter, wdyt? |
ah yes, that makes the definition more clear |
you're welcome @vchrombie |
planned metrics are implemented, so closing this issue |
Opening this issue to discuss the possible metrics which can be extracted from the gitlab raw data for
gitlabqm
enricher.The text was updated successfully, but these errors were encountered: