GitHub user riskpeep added a comment to the discussion: PR Coding time affected by (squash) merge strategy
We are seeing this issue as well. We're using BitBucket, and, at least for us, we see that most PRs have a pr_coding_time of 0. We have squash commits turned on. In BB, when a squash merge is committed, BB updates the commits on the PR and removes the earlier commits and only shows the squash commit. Dora then, picks up the PR and finds only the commit mentioned in the PR. Interstingly, the other commits ARE mentioned in the comment history for the PR, but Devlake doesn't seem to pick that up. GitHub link: https://github.com/apache/incubator-devlake/discussions/8440#discussioncomment-13370601 ---- This is an automatically sent email for dev@devlake.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@devlake.apache.org
