rodrigoluizs opened a new issue, #8381:
URL: https://github.com/apache/incubator-devlake/issues/8381
<!--
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
Hi folks,
We’re using DevLake to track DORA metrics, and we’ve noticed that automated
commits and PRs (e.g., from Renovate or Dependabot) are skewing our metrics —
especially lead time and deployment frequency. These automated changes usually
have close to zero code time and very low pickup/review time, since engineers
often merge them as soon as the test pipelines pass. In some cases, they are
even automatically merged when all the pipelines succeed.
**Is there already a way in DevLake to exclude commits or PRs from specific
authors (like bots) when calculating DORA metrics**? If not, we’d be interested
in contributing a solution, as we believe this could be useful for others as
well.
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: dev-unsubscr...@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
