klesh opened a new issue, #6103: URL: https://github.com/apache/incubator-devlake/issues/6103
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case _No response_ ### Description Currently, Change Lead Time calculation relies on the `PRs`, `Commits`, and `DeploymentCommits`. However, some of them might not be available in some use cases: - #5269 trunk-based development doesn't have any PR at all, every developer would push his/her Changes to the branch directly. In this case, each push might contain multiple `commits` and be considered a **PR** - #5909 deployment on **PR Merge** would produce required entities(`PRs`, `Commits`, and `DeploymentCommits`) just fine, but the catch is that the `PR.merge_commit_sha`s come from **Feature Branches** and **NOT** being included in the `main` branch when using **Squash and Merge** method, so it is impossible to connect `PR`s to their correct `Deployments`. **Note that in the above cases, the information we need is only available during the CI/CD runtime and then lost forever, in other words, it can't be recovered afterward when collecting.** In general, the data we need for CLT calculation might not be available or correct in some cases, we need a universal solution to support them. ### Related issues - 5909 - 5269 ### Are you willing to submit a 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]
