CVidCev opened a new issue, #8542:
URL: https://github.com/apache/incubator-devlake/issues/8542
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## Question
We're trying to use the DORA Metrics dashboard thus we are making sure that
the values are accurate. We already validated the deployment frequency, so the
count matches but now we're checking the lead time for changes and we noted
something, we can't see the MR's within the table and now I think I know why,
most of our MR's dont have pr_coding_time and even if that's not the reason, we
only have values on the average PR deploy time, so the metrics seem
innaccurate. Some of our PR's do have pr_coding_time, but I couldn't find any
different so I conducted an experiment:
I made a commit to development, waited a day, created a MR from develop to
main, merged it and then waited another day to deploy, I can only see the
average PR deploy time so, What's the meaning of the coding time? Do I have to
make more than one commit? Do I have to make a branch?
We would like to know what are the requisites for a PR/MR to have a value in
that column.
Thanks in advance!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
