danieljuhasz93 opened a new issue, #6646: URL: https://github.com/apache/incubator-devlake/issues/6646
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened **Context:** We use the GitFlow branching strategy in our team. This means that we only merge the changes to the main branch when we are ready for a (internal) release. Because of this pull requests from the develop to the main branch can include several commits. **Issue:** We encountered an issue with the calculation of the Lead Time for Changes DORA metric. If a pull request has more than 250 commits, then only the first 250 commits are retrieved, and the oldest retrieved commit is treated as the first commit of the pull request. This leads to the incorrect calculation of the PR coding time and PR change lead time. ### What do you expect to happen I would expect that all of the commits in a PR are retrieved instead of only the first 250 commits. ### How to reproduce Prerequisites: a merged PR with more than 250 commits should exist in the repository. 1. Collect data from the beforementioned repository with the DORA option enabled 2. Inspect the Lead Time for Changes values on the built-in DORA dashboard. ### Anything else The issue occurs every time, if we have a PR with more than 250 commits. ### Version v0.18.0 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
